https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #18 from Iain Sandoe ---
I'm testing regularly on macOS 10.14 (darwin18) - which I assume is the version
you meant?
Also on 8.3 and 9.2 .. (the results are posted to @testresults).
There was a PCH fixed (but that only manifested
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #17 from Steve Ellcey ---
The bug I was seeing on aarch64 turns out to be PR 91404. It has now been
fixed. I don't know if that patch will also fix the original bug seen on
Darwin or not.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #16 from Steve Ellcey ---
I built ggc-page.c with GCC_DEBUG_LEVEL 5 and I see:
Allocating object, requested size=360, actual=360 at 0x8726c210 on
0x10549200
Freeing object, actual size=360, at 0x8726c210 on 0x10549200
But
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
Steve Ellcey changed:
What|Removed |Added
CC||sje at gcc dot gnu.org
--- Comment #14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #13 from Richard Biener ---
It might help (a little bit...) if you can run cc1plus in a debugger and at
the point of the crash print the value of p and provide a backtrace.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #12 from Vincent ---
Thanks, Andrew.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #11 from Andrew Pinski ---
(In reply to Vincent from comment #10)
> Yes, sorry about that.
> Alas, I don't use them...
https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction might be a good thing to
look into.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #10 from Vincent ---
Yes, sorry about that.
Alas, I don't use them...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #9 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #8)
> You still have not answered my question about precompiled headers? Do you
> use them?
If so the workaround is not to use them at all. See PR 61250 for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #8 from Andrew Pinski ---
You still have not answered my question about precompiled headers? Do you use
them?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #7 from Vincent ---
I understand.
It might have something to do with 67650, which was been in gcc since 2005, and
is fully reproducible until now (8.2.0). It seems to be a memory error too.
Sadly, nobody ever gave it a try.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #6 from Andrew Pinski ---
Read https://gcc.gnu.org/bugs/ .
There is nothing we can help you with without any way of trying to reproduce
the bug.
A crash in ggc_set_mark means one of two things:
* Precompiled Headers were used and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #5 from Vincent ---
Hmm, hard to do, it is monumental and contains a ton of stuff I cannot share...
Sorry about that, I realize it makes diagnosis quite difficult.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #4 from Andrew Pinski ---
Can you add -save-temps and attach the preprocessed source?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #3 from Vincent ---
It on MacOS Mojave 10.14.2.
The command line options are:
/usr/local/bin/g++-8 -c -DNDEBUG -O3 -fvisibility=hidden -Wall -Wextra
-pedantic-errors -DDARWIN -std=c++17 -fvisibility-inlines-hidden
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
--- Comment #2 from Andrew Pinski ---
Oh what host is this on?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89179
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
19 matches
Mail list logo
