public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominique.pelletier at polymtl dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56818] [meta-bug] fortran-dev bugs
Date: Tue, 02 Apr 2013 19:03:00 -0000	[thread overview]
Message-ID: <bug-56818-4-hmTBjCBZBz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56818-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56818

Dominique Pelletier <dominique.pelletier at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dominique.pelletier at
                   |                            |polymtl dot ca

--- Comment #1 from Dominique Pelletier <dominique.pelletier at polymtl dot ca> 2013-04-02 19:03:05 UTC ---
DP@P-DP /cygdrive/c/users/dp/Desktop/metcalf
$ gfortran -v -c bug_report.f03
Using built-in specs.
COLLECT_GCC=C:\Program Files (x86)\gfortran\bin\gfortran.exe
Target: mingw32
Configured with: ../gcc-trunk/configure --prefix=/mingw
--enable-languages=c,fortran,lto --with-gmp=/home/brad/gfortran/dependencies
--disable-werror --enable-threads --enable-nls --build=i586-pc-mingw32
--enable-libgomp --enable-shared --disable-win32-registry --with-dwarf2
--disable-sjlj-exceptions --enable-lto --build=mingw32
--enable-version-specific-runtime-libs
Thread model: win32
gcc version 4.8.0 20130302 (experimental) [trunk revision 196403] (GCC)
COLLECT_GCC_OPTIONS='-v' '-c' '-mtune=i386' '-march=i386'
 c:/program files (x86)/gfortran/bin/../libexec/gcc/mingw32/4.8.0/f951.exe
bug_report.f03 -quiet -dumpbase bug_report.f03 -mtune=i386 -march=i386 -auxbase
bug_report -version -fintrinsic-modules-path c:/program files
(x86)/gfortran/bin/../lib/gcc/mingw32/4.8.0/finclude -o
C:\cygwin\tmp\cc7RQyBk.s
GNU Fortran (GCC) version 4.8.0 20130302 (experimental) [trunk revision 196403]
(mingw32)
        compiled by GNU C version 4.8.0 20130302 (experimental) [trunk revision
196403], GMP version 5.0.2, MPFR version 3.1.0, MPC version 0.9
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU Fortran (GCC) version 4.8.0 20130302 (experimental) [trunk revision 196403]
(mingw32)
        compiled by GNU C version 4.8.0 20130302 (experimental) [trunk revision
196403], GMP version 5.0.2, MPFR version 3.1.0, MPC version 0.9
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
f951.exe: internal compiler error: Segmentation fault
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.


       reply	other threads:[~2013-04-02 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-56818-4@http.gcc.gnu.org/bugzilla/>
2013-04-02 19:03 ` dominique.pelletier at polymtl dot ca [this message]
2013-04-02 19:04 ` dominique.pelletier at polymtl dot ca
2013-06-20 18:37 ` dominiq at lps dot ens.fr
2014-06-08 15:11 ` fxcoudert at gcc dot gnu.org
2020-07-29 10:18 ` markeggleston at gcc dot gnu.org
2020-07-29 14:32 ` dominiq at lps dot ens.fr
2023-04-08 18:37 ` anlauf at gcc dot gnu.org

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-56818-4-hmTBjCBZBz@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: link
Be 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).