Bug 26099 - JSC fails to build in OpenBSD/amd64 - COMPILE_ASSERT failed in JITStubs
Summary: JSC fails to build in OpenBSD/amd64 - COMPILE_ASSERT failed in JITStubs
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Other
: P2 Normal
Assignee: Nobody
URL:
Keywords: Gtk
Depends on:
Blocks:
 
Reported: 2009-05-30 17:12 PDT by Landry Breuil
Modified: 2010-01-07 09:23 PST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Landry Breuil 2009-05-30 17:12:07 PDT 
1.1.5 builded fine, 1.1.8 fails with the following message :
JavaScriptCore/jit/JITStubs.cpp:125: error: array bound is not an integer constant
JavaScriptCore/jit/JITStubs.cpp:126: error: array bound is not an integer constant
JavaScriptCore/jit/JITStubs.cpp:127: error: array bound is not an integer constant
probably a side effect of r43374.

This is on OpenBSD/amd64 with g++ 4.2.4.
Commenting the three COMPILE_ASSERT makes the error go away, but it's an ugly workaround.
Comment 1 Jan Alonzo 2009-07-17 16:48:03 PDT 
(In reply to comment #0)
> 1.1.5 builded fine, 1.1.8 fails with the following message :
> JavaScriptCore/jit/JITStubs.cpp:125: error: array bound is not an integer
> constant
> JavaScriptCore/jit/JITStubs.cpp:126: error: array bound is not an integer
> constant
> JavaScriptCore/jit/JITStubs.cpp:127: error: array bound is not an integer
> constant
> probably a side effect of r43374.
> 
> This is on OpenBSD/amd64 with g++ 4.2.4.
> Commenting the three COMPILE_ASSERT makes the error go away, but it's an ugly
> workaround.

Hi Landry, does it still fail in your setup?
Comment 2 Landry Breuil 2009-07-18 00:18:09 PDT 
Yes, as of webkitgtk 1.1.10 it still fails. I can't test 1.1.11 atm, as we don't ship 'unstable' releases of libsoup from 2.27.x branch..
Comment 3 Landry Breuil 2010-01-07 09:23:55 PST 
As of webkit 1.1.18, this is not needed anymore. No idea what changed to fix it.