public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/65777] SPECOMP component 362.fma3d fails with error "SIGSEGV, segmentation fault occurred"
[not found] <bug-65777-4@http.gcc.gnu.org/bugzilla/>
@ 2015-04-15 22:01 ` pinskia at gcc dot gnu.org
2015-04-16 7:44 ` rguenth at gcc dot gnu.org
2015-04-16 20:51 ` rajendray_14 at yahoo dot co.in
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-04-15 22:01 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65777
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c |middle-end
Target Milestone|--- |4.8.3
Severity|critical |normal
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Have you tried increasing the stack size limit?
Also since this is with SUSE's compiler have you reported this to them?
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug middle-end/65777] SPECOMP component 362.fma3d fails with error "SIGSEGV, segmentation fault occurred"
[not found] <bug-65777-4@http.gcc.gnu.org/bugzilla/>
2015-04-15 22:01 ` [Bug middle-end/65777] SPECOMP component 362.fma3d fails with error "SIGSEGV, segmentation fault occurred" pinskia at gcc dot gnu.org
@ 2015-04-16 7:44 ` rguenth at gcc dot gnu.org
2015-04-16 20:51 ` rajendray_14 at yahoo dot co.in
2 siblings, 0 replies; 3+ messages in thread
From: rguenth at gcc dot gnu.org @ 2015-04-16 7:44 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65777
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2015-04-16
Version|unknown |4.8.3
Target Milestone|4.8.3 |---
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Waiting for a testcase and more details (compiler options?). If you use -Ofast
(or -fstack-arrays) indeed you need to raise the stack limit size (and with OMP
that might not be enough as thread stack size might be too small again).
^ permalink raw reply [flat|nested] 3+ messages in thread* [Bug middle-end/65777] SPECOMP component 362.fma3d fails with error "SIGSEGV, segmentation fault occurred"
[not found] <bug-65777-4@http.gcc.gnu.org/bugzilla/>
2015-04-15 22:01 ` [Bug middle-end/65777] SPECOMP component 362.fma3d fails with error "SIGSEGV, segmentation fault occurred" pinskia at gcc dot gnu.org
2015-04-16 7:44 ` rguenth at gcc dot gnu.org
@ 2015-04-16 20:51 ` rajendray_14 at yahoo dot co.in
2 siblings, 0 replies; 3+ messages in thread
From: rajendray_14 at yahoo dot co.in @ 2015-04-16 20:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65777
--- Comment #3 from raj <rajendray_14 at yahoo dot co.in> ---
I'm using Intel Compiler version 15.0 and the update 2. Both has the similar
issue and it could be because the libraries from the GCC version installed. I
tried setting stack size to unlimited, 190 MB to 16 GB, none worked.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-04-16 20:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-65777-4@http.gcc.gnu.org/bugzilla/>
2015-04-15 22:01 ` [Bug middle-end/65777] SPECOMP component 362.fma3d fails with error "SIGSEGV, segmentation fault occurred" pinskia at gcc dot gnu.org
2015-04-16 7:44 ` rguenth at gcc dot gnu.org
2015-04-16 20:51 ` rajendray_14 at yahoo dot co.in
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).