Closed
Bug 845277
Opened 10 years ago
Closed 10 years ago
Asan builds burning with "js/src/jsproxy.h:346:7: error: visibility does not match previous declaration"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: emorley, Assigned: espindola)
References
Details
Attachments
(1 file)
356 bytes,
patch
|
bholley
:
review+
|
Details | Diff | Splinter Review |
Started on this push: https://tbpl.mozilla.org/?noignore=1&rev=f9ece777368e { In file included from /builds/slave/m-cen-l64-dbg-asan-00000000000/build/js/src/jsobjinlines.h:22: /builds/slave/m-cen-l64-dbg-asan-00000000000/build/js/src/jsproxy.h:346:7: error: visibility does not match previous declaration class JS_FRIEND_API(AutoEnterPolicy) }
Reporter | ||
Comment 1•10 years ago
|
||
decoder: The first bad revision is: decoder: changeset: 122943:51483e470216 decoder: user: Bobby Holley <bobbyholley@snip> decoder: date: Mon Feb 25 13:54:18 2013 -0800 decoder: summary: Bug 836301 - Hoist some assertions, remove a bunch of no-op trap overrides, and add assertions that we've entered our policy. r=mrbkap
Blocks: 836301
Assignee | ||
Comment 2•10 years ago
|
||
The clang used is 170890.
Assignee | ||
Comment 3•10 years ago
|
||
(In reply to Rafael Ávila de Espíndola (:espindola) from comment #2) > The clang used is 170890. Which is the one we had been using. I thought this could be a bug in newer clangs, but was change in m-c.
Assignee | ||
Comment 4•10 years ago
|
||
Assignee: general → respindola
Status: NEW → ASSIGNED
Attachment #718384 -
Flags: review?(bobbyholley+bmo)
Comment 5•10 years ago
|
||
See also bug 845215.
Updated•10 years ago
|
Attachment #718384 -
Flags: review?(bobbyholley+bmo) → review+
Assignee | ||
Comment 6•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a2e147b93af6
Reporter | ||
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/a2e147b93af6
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in
before you can comment on or make changes to this bug.
Description
•