-
Notifications
You must be signed in to change notification settings - Fork 8
Add conservative stack scanning bug found in Chromium #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
softdev.bib
Outdated
| } | ||
| @misc{chromium20cssbug, | ||
| title = {Octane benchmark suite}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh, copy paste bug. I'll push a fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I'm a little unsure what to call this. Can I use the lengthy title of the bug report?
"base::Optional when compiled with clang leads to memory layout that is incompatible with conservative stack scanning"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. Let's try that as the title and see how we feel in a day or so!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
|
Please squash. |
087bbfe to
ae982d7
Compare
|
Squashed |
|
bors r+ |
|
Build failed: |
|
Fixed: 8454058 |
|
Please squash. |
8454058 to
921357c
Compare
|
Squashed |
|
bors r+ |
|
Build succeeded: |
No description provided.