https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
Avi Kivity changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
--- Comment #6 from rguenther at suse dot de ---
On Fri, 26 Sep 2014, a...@cloudius-systems.com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
>
> --- Comment #5 from Avi Kivity ---
> Richard, may I send you the test case privatel
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
--- Comment #5 from Avi Kivity ---
Richard, may I send you the test case privately?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
--- Comment #4 from rguenther at suse dot de ---
On Thu, 25 Sep 2014, a...@cloudius-systems.com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
>
> --- Comment #2 from Avi Kivity ---
> I managed to narrow it down to 400 lines (befo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
Markus Trippelsdorf changed:
What|Removed |Added
CC||trippels at gcc dot gnu.org
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
--- Comment #2 from Avi Kivity ---
I managed to narrow it down to 400 lines (before preprocessing), strangely in
one file. Now, practically anything I touch turns the segfault into link
errors.
Is this useful? I could share it privately.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=6
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
