public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/60088] [MingW] Segfault when using quad precision and -march=native on gfortran Date: Thu, 06 Feb 2014 02:23:00 -0000 [thread overview] Message-ID: <bug-60088-4-xkXoZzmvL1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60088-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60088 kargl at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kargl at gcc dot gnu.org Component|fortran |target Summary|Segfault when using quad |[MingW] Segfault when using |precision and -march=native |quad precision and |on gfortran |-march=native on gfortran --- Comment #2 from kargl at gcc dot gnu.org --- This is not a fortran specific problem as it works with i386-*-freebsd. This also looks like it is coming from the c.l.f thread https://groups.google.com/forum/#!topic/comp.lang.fortran/gcXN-AcjsIw Looks like mingw is broken.
next prev parent reply other threads:[~2014-02-06 2:23 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-06 1:41 [Bug fortran/60088] New: " thatcadguy at gmail dot com 2014-02-06 1:42 ` [Bug fortran/60088] " thatcadguy at gmail dot com 2014-02-06 2:23 ` kargl at gcc dot gnu.org [this message] 2014-02-06 2:25 ` [Bug target/60088] [MingW] " thatcadguy at gmail dot com 2014-02-06 3:44 ` [Bug target/60088] " jvdelisle at gcc dot gnu.org 2014-02-06 3:56 ` sgk at troutmask dot apl.washington.edu 2014-02-06 4:42 ` thatcadguy at gmail dot com 2014-02-06 5:47 ` kargl at gcc dot gnu.org 2014-02-06 11:12 ` dominiq at lps dot ens.fr 2014-02-06 19:34 ` dominiq at lps dot ens.fr 2014-02-06 21:56 ` thatcadguy at gmail dot com 2014-02-06 22:02 ` thatcadguy at gmail dot com 2014-02-06 22:09 ` kargl at gcc dot gnu.org 2014-02-06 22:47 ` jouko.orava at iki dot fi 2014-02-06 22:59 ` thatcadguy at gmail dot com 2014-02-07 3:04 ` jouko.orava at iki dot fi 2014-02-07 3:35 ` jouko.orava at iki dot fi 2014-02-07 4:22 ` thatcadguy at gmail dot com 2014-02-07 4:59 ` jouko.orava at iki dot fi 2014-02-07 6:14 ` jouko.orava at iki dot fi 2014-02-07 16:34 ` thatcadguy at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-60088-4-xkXoZzmvL1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).