https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #28 from Randy MacLeod ---
Alex, thanks for confirming, I was worried that it was one of the _perfectly_
sensible local patches we have in YP. ;-)
FYI, a local toolchain expert has started working on this defect so stay tuned
/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Alex Potapenko changed:
What|Removed |Added
CC||opotapenko at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #26 from Segher Boessenkool ---
I still can't reproduce the problem, and I don't see where the null
pointer is coming from either. Someone who can reproduce the problem
will have to do some debugging. Sorry.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #25 from Randy MacLeod ---
Any progress or need for additional information?
What should I expect over the coming weeks?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #24 from Randy MacLeod ---
This ICE still happens with gcc-7.2.
Here's the stacktrace:
(gdb) bt
#0 store_expr_with_bounds (exp=exp@entry=0x76275900,
target=target@entry=0x7625d660, call_param_p=call_param_p@entry=0,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #23 from Randy MacLeod ---
Here is the 'bt' and 'bt full' with line numbers and symbols. YP diff to enable
this is below as well. Thanks for you patience as I re-learn these ropes.
Program received signal SIGSEGV, Segmentation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #22 from Randy MacLeod ---
Yes, the host is an x86-64-linux system running Ubuntu-16.04.1.
The cross-compiler was built using the Open Embedded (OE) build system so of
course, it's not part of Ubuntu.
I did get a better backtrace
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #21 from Segher Boessenkool ---
Hrm, those ?? are a bit worrying, is that normal on x86_64-linux
(that is what this is, as host?)
I also don't see line numbers.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #20 from Randy MacLeod ---
I can try! ;) How's this:
$ gdb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #19 from Segher Boessenkool ---
(In reply to Randy MacLeod from comment #18)
> 2. The "smaller reproducer with manual work-around " DOES STILL result in an
> ICE as does the libjpeg-turbo build as you'd expect.
I still cannot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #18 from Randy MacLeod ---
With both patches applied:
1. The "minimal testcase produced by the delta utility" no longer ICEs the
toolchain.
2. The "smaller reproducer with manual work-around " DOES STILL result in an
ICE as does the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #17 from Randy MacLeod ---
Back from vacation, I plan to test the latest patch this week.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #16 from Will Schmidt ---
(In reply to Bill Schmidt from comment #13)
> CCing Will Schmidt for the general gimple-folding issue of built-in calls
> with missing LHSes.
revision 250185 has been committed to handle the gimple-folding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Segher Boessenkool changed:
What|Removed |Added
Attachment #41722|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #14 from Segher Boessenkool ---
Created attachment 41722
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41722=edit
second patch, for the original problem
This one should solve the original problem.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Bill Schmidt changed:
What|Removed |Added
CC||willschm at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Bill Schmidt changed:
What|Removed |Added
CC||wschmidt at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #11 from Segher Boessenkool ---
The original testcase still ICEs ("smaller reproducer" I never got to fail).
(trunk, no options whatsoever):
81317-1.c: In function 'jsimd_ycc_rgb_convert_altivec':
81317-1.c:184:6: internal compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Segher Boessenkool changed:
What|Removed |Added
Attachment #41718|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Segher Boessenkool changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |segher at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #7 from Randy MacLeod ---
Is anyone working on this bug? I'm not pushing, but rather trying to understand
what to expect.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #6 from Randy MacLeod ---
Created attachment 41682
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41682=edit
smaller reproducer with manual work-around
The work-around clearly isn't a viable one.
I believe that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
--- Comment #5 from Randy MacLeod ---
I agree that the creduce output should be ignored. :(
I ran 'delta' again with a manually cleaned up input and I got a minimal
reproducer that is shorter:
wc -l output:
old:
4756 /tmp/jdcolor-altivec.i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81317
Andrew Pinski changed:
What|Removed |Added
Target||powerpc-oe-linux
Component|c
26 matches
Mail list logo
