public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vdanjean at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18753] New: GCC internal error with -O3 and -finstrument-functions with gcc-3.4
Date: Wed, 01 Dec 2004 11:36:00 -0000	[thread overview]
Message-ID: <20041201113619.18753.vdanjean@free.fr> (raw)

The internal error can be triggered with the following code :

static inline void foo(void) { }
void bar(void) { foo(); }

with the command line :
gcc -O3 -finstrument-functions -c test.c

I obtain :
test.c: In function `foo':
test.c:2: internal compiler error: in cgraph_expand_function, at cgraphunit.c:540
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-3.4/README.Bugs>.

I do not have the bug with -O2 instead -O3, nor without  -finstrument-functions,
nor with gcc 3.3

I tried the following compilers :
* plain gcc-3.4.0 on ia64 :
danjeanv@ns0:~$ ~perachem/bin/gcc  -v
Reading specs from /home_nfs/perache/bin/lib/gcc/ia64-unknown-linux-gnu/3.4.0/specs
Configured with: ./configure --enable-languages=c,c++ --enable-threads=posix
--prefix=/home_nfs/perache/bin --bindir=/home_nfs/perache/bin
Thread model: posix
gcc version 3.4.0
* gcc-3.4.2 + current debian patches on ia64 :
danjeanv@ns0:~$ gcc -v
Reading specs from
/home_nfs/danjean/stow/gcc-3.4.2/bin/../lib/gcc/ia64-unknown-linux-gnu/3.4.2/specs
Configured with: ../src/configure --prefix=/home_nfs/danjean/
Thread model: posix
gcc version 3.4.2 (Debian)
* gcc-3.4.3 + debian patch on x86 (current gcc-3.4 version in sid debian
distribution)
Reading specs from /usr/lib/gcc/i486-linux/3.4.4/specs
Configured with: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr
--libexecdir=/usr/lib --with-gxx-include-dir=/usr/include/c++/3.4
--enable-shared --with-system-zlib --enable-nls --without-included-gettext
--program-suffix=-3.4 --enable-__cxa_atexit --enable-libstdcxx-allocator=mt
--enable-clocale=gnu --enable-libstdcxx-debug --enable-java-gc=boehm
--enable-java-awt=gtk --disable-werror i486-linux
Thread model: posix
gcc version 3.4.4 20041128 (prerelease) (Debian 3.4.3-2)

-- 
           Summary: GCC internal error with -O3 and -finstrument-functions
                    with gcc-3.4
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: vdanjean at free dot fr
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-12-01 11:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 11:36 vdanjean at free dot fr [this message]
2004-12-01 11:58 ` [Bug c/18753] [3.4 Regression] " belyshev at lubercy dot com
2004-12-01 12:04 ` [Bug middle-end/18753] [3.4 Regression] ICE with " reichelt at gcc dot gnu dot org
2004-12-01 12:36 ` pinskia at gcc dot gnu dot 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=20041201113619.18753.vdanjean@free.fr \
    --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).