Closed
Bug 1019003
Opened 10 years ago
Closed 10 years ago
Build warning: ‘visibility’ attribute ignored [-Wattributes] in TypedArrayObject.cpp
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: bbouvier, Assigned: Waldo)
References
Details
(Whiteboard: [qa-])
Attachments
(2 files, 1 obsolete file)
1.78 KB,
patch
|
bbouvier
:
review+
Sylvestre
:
approval-mozilla-aurora+
Sylvestre
:
approval-mozilla-beta-
Sylvestre
:
approval-mozilla-esr24+
|
Details | Diff | Splinter Review |
1002 bytes,
patch
|
Details | Diff | Splinter Review |
These ArrayClassPtr are already defined as JS_FRIEND_DATA in jsfriendapi.h, so it doesn't seem needed in TypedArrayObject.cpp.
The shell compiles without any issue when disabling it. The full browser does too (gcc 4.8.2). Do you think it'd need a try build?
In file included from /home/ben/code/moz/builds/wd64/js/src/Unified_cpp_js_src11.cpp:28:0:
/home/ben/code/moz/inbound/js/src/vm/TypedArrayObject.cpp:2105:1251: warning: ‘visibility’ attribute ignored [-Wattributes]
IMPL_TYPED_ARRAY_JSAPI_CONSTRUCTORS(Float32, float)
Attachment #8432552 -
Flags: review?(jwalden+bmo)
Assignee | ||
Comment 1•10 years ago
|
||
Comment on attachment 8432552 [details] [diff] [review]
warning-js-default-visibility.patch
Review of attachment 8432552 [details] [diff] [review]:
-----------------------------------------------------------------
I wouldn't bother tryservering, myself.
Attachment #8432552 -
Flags: review?(jwalden+bmo) → review+
Reporter | ||
Comment 3•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
Reporter | ||
Comment 5•10 years ago
|
||
[Aurora/Beta Approval Request Comment]
Bug caused by (feature/regressing bug #): bug 991981
User impact if declined: can't build with Mingw (as stated in bug 1021582, it's used for cross-compilation of the Tor bundle project).
Testing completed (on m-c, etc.): m-i, m-c
Risk to taking this patch (and alternatives if risky): no risk, build passed on all platforms.
String or IDL/UUID changes made by this patch: n/a
[ESR Approval Request Comment]
If this is not a sec:{high,crit} bug, please state case for ESR consideration:
User impact if declined: can't build with Mingw (as stated in bug 1021582, it's used for cross-compilation of the Tor bundle project).
Fix Landed on Version: current Nightly.
Risk to taking this patch (and alternatives if risky): no risk, build passed on all platforms.
String or UUID changes made by this patch: n/a
Apparently, there was a build error caused by this on mingw (see also bug 1021582), so we should uplift that to all versions that received the uplift for bug 991981.
Carrying forward r+ from Waldo.
Attachment #8432552 -
Attachment is obsolete: true
Attachment #8435639 -
Flags: review+
Attachment #8435639 -
Flags: approval-mozilla-esr24?
Attachment #8435639 -
Flags: approval-mozilla-beta?
Attachment #8435639 -
Flags: approval-mozilla-aurora?
Updated•10 years ago
|
status-firefox30:
--- → affected
status-firefox31:
--- → affected
status-firefox32:
--- → fixed
status-firefox-esr24:
--- → affected
Comment 7•10 years ago
|
||
Comment on attachment 8435639 [details] [diff] [review]
bug1019003.patch
Too late for beta/release.
Accepting for ESR since the Tor project is using esr (like Debian).
Attachment #8435639 -
Flags: approval-mozilla-esr24?
Attachment #8435639 -
Flags: approval-mozilla-esr24+
Attachment #8435639 -
Flags: approval-mozilla-beta?
Attachment #8435639 -
Flags: approval-mozilla-beta-
Attachment #8435639 -
Flags: approval-mozilla-aurora?
Attachment #8435639 -
Flags: approval-mozilla-aurora+
Comment 8•10 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/082d356f509c
esr24 is going to need a branch-specific patch.
Flags: needinfo?(benj)
Keywords: branch-patch-needed
Comment 9•10 years ago
|
||
Ben, should this have tests or be in the test suite? Thanks!
Flags: in-testsuite?
Assignee | ||
Comment 10•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Assignee: benj → jwalden+bmo
Comment 11•10 years ago
|
||
Comment 12•10 years ago
|
||
This just missed the ESR 24.6.0 build #2. Can this be worked around in the 24.6.0 cycle so that we don't have to respin?
Reporter | ||
Comment 13•10 years ago
|
||
(In reply to Liz Henry :lizzard from comment #9)
> Ben, should this have tests or be in the test suite? Thanks!
We can't actually test that, as it's a build warning in the best case, a build failure for cross compilation in the worst case (and that cross compilation build is not included in our CI platform).
Flags: in-testsuite? → in-testsuite-
You need to log in
before you can comment on or make changes to this bug.
Description
•