https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #30 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:2f83ea87ee328d337f87d4430861221be9babe1e
commit r15-1582-g2f83ea87ee328d337f87d4430861221be9babe1e
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #29 from Richard Biener ---
(In reply to Jürgen Reuter from comment #28)
> Richard, unfortunately the fix (it seems it was committed to gcc git master
> on last Friday) did not fix our problem yet. The original test case still
> segf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #28 from Jürgen Reuter ---
Richard, unfortunately the fix (it seems it was committed to gcc git master on
last Friday) did not fix our problem yet. The original test case still
segfaults:
Backtrace for this error:
#0 0x7f36f52a3a6c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #27 from Jürgen Reuter ---
(In reply to Jürgen Reuter from comment #26)
> (In reply to Richard Biener from comment #24)
> > (In reply to Jürgen Reuter from comment #23)
> > > Created attachment 58486 [details]
> > > Shorter reproduce
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #26 from Jürgen Reuter ---
(In reply to Richard Biener from comment #24)
> (In reply to Jürgen Reuter from comment #23)
> > Created attachment 58486 [details]
> > Shorter reproducer
> >
> > This is a shorter reproducer, two files of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #25 from Jürgen Reuter ---
(In reply to Richard Biener from comment #24)
> (In reply to Jürgen Reuter from comment #23)
> > Created attachment 58486 [details]
> > Shorter reproducer
> >
> > This is a shorter reproducer, two files of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #24 from Richard Biener ---
(In reply to Jürgen Reuter from comment #23)
> Created attachment 58486 [details]
> Shorter reproducer
>
> This is a shorter reproducer, two files of a few hundred lines each. It
> seems that the problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #23 from Jürgen Reuter ---
Created attachment 58486
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58486&action=edit
Shorter reproducer
This is a shorter reproducer, two files of a few hundred lines each. It seems
that the pro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
Richard Biener changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #20 from kargls at comcast dot net ---
(In reply to Jürgen Reuter from comment #19)
> Created attachment 58476 [details]
> First independent reproducer
It appears to be a striding issue. The loops at formf.f:507 is
DO 206 I=
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #19 from Jürgen Reuter ---
Created attachment 58476
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58476&action=edit
First independent reproducer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #18 from Richard Biener ---
(In reply to Jürgen Reuter from comment #17)
> (In reply to Richard Biener from comment #16)
> > (In reply to Jürgen Reuter from comment #15)
> > > I fund the culprit commit in the gcc master, it is:
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #17 from Jürgen Reuter ---
(In reply to Richard Biener from comment #16)
> (In reply to Jürgen Reuter from comment #15)
> > I fund the culprit commit in the gcc master, it is:
> > https://gcc.gnu.org/git/?p=gcc.git;a=commit;
> > h=1f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #16 from Richard Biener ---
(In reply to Jürgen Reuter from comment #15)
> I fund the culprit commit in the gcc master, it is:
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;
> h=1fe55a1794863b5ad9eeca5062782834716016b2
> by Richard B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #15 from Jürgen Reuter ---
I fund the culprit commit in the gcc master, it is:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=1fe55a1794863b5ad9eeca5062782834716016b2
by Richard Biener on the tree-optimization. Now I will try helping
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #14 from Jürgen Reuter ---
(In reply to Jürgen Reuter from comment #13)
> The daily bump in the morning of Friday, June 14,
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;
> h=028cd77db322d21312680c9a0a7c30565854f577
> shows the segm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #13 from Jürgen Reuter ---
The daily bump in the morning of Friday, June 14,
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=028cd77db322d21312680c9a0a7c30565854f577
shows the segmentation fault, so the culprit comment must have happe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #12 from Sam James ---
I would just git bisect instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #11 from Jürgen Reuter ---
(In reply to Jürgen Reuter from comment #10)
> (In reply to Jürgen Reuter from comment #9)
> > Also at the daily bump shortly after midnight morning of June 11,
> > https://gcc.gnu.org/git/?p=gcc.git;a=comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #10 from Jürgen Reuter ---
(In reply to Jürgen Reuter from comment #9)
> Also at the daily bump shortly after midnight morning of June 11,
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;
> h=097bc0aebaed58c11c738ea61da723cca950e5b1
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #9 from Jürgen Reuter ---
Also at the daily bump shortly after midnight morning of June 11,
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=097bc0aebaed58c11c738ea61da723cca950e5b1
the reproducer still runs fine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #8 from Jürgen Reuter ---
(In reply to Jürgen Reuter from comment #6)
> (In reply to kargls from comment #5)
> > (In reply to Jürgen Reuter from comment #4)
> > > Created attachment 58462 [details]
> > > Input file that triggers the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #7 from Jürgen Reuter ---
First data point:
after the commit from Uros,
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8bb6b2f4ae19c3aab7d7a5e5c8f5965f89d90e01
at Sun, 9 Jun 2024 10:09:13
all was still fine.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #6 from Jürgen Reuter ---
(In reply to kargls from comment #5)
> (In reply to Jürgen Reuter from comment #4)
> > Created attachment 58462 [details]
> > Input file that triggers the test case with segmentation fault
> >
> > This test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
kargls at comcast dot net changed:
What|Removed |Added
CC||kargls at comcast dot net
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
--- Comment #4 from Jürgen Reuter ---
Created attachment 58462
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58462&action=edit
Input file that triggers the test case with segmentation fault
This test case needs Whizard 3.1.4 to be downlo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115528
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
29 matches
Mail list logo
