public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "galtgendo at o2 dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50506] gcc fails at assembly with -O1 while inlining is forced
Date: Sat, 24 Sep 2011 14:18:00 -0000	[thread overview]
Message-ID: <bug-50506-4-d1byTGT3CQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50506-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Rafał Mużyło <galtgendo at o2 dot pl> 2011-09-24 13:38:47 UTC ---
Well,...
The actual result was quite a bit more interesting, cause:
Using built-in specs.
COLLECT_GCC=/usr/i686-pc-linux-gnu/gcc-bin/4.5.3/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/lto-wrapper
Target: i686-pc-linux-gnu
Configured with:
/mnt/workbox/builds/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/configure
--prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.5.3
--includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.5.3/include
--datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3
--mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3/man
--infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.5.3/info
--with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.5.3/include/g++-v4
--host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec
--disable-fixed-point --with-ppl --with-cloog --disable-ppl-version-check
--with-cloog-include=/usr/include/cloog-ppl --enable-lto --enable-nls
--without-included-gettext --with-system-zlib --disable-werror
--enable-secureplt --disable-multilib --enable-libmudflap --disable-libssp
--enable-libgomp
--with-python-dir=/share/gcc-data/i686-pc-linux-gnu/4.5.3/python
--enable-checking=release --disable-libgcj --with-arch=i686 --enable-objc-gc
--enable-languages=c,c++,objc,fortran --enable-shared --enable-threads=posix
--enable-__cxa_atexit --enable-clocale=gnu
--with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.5.3-r1 p1.0,
pie-0.4.5' --disable-libstdcxx-pch
Thread model: posix
gcc version 4.5.3 (Gentoo 4.5.3-r1 p1.0, pie-0.4.5) 
COLLECT_GCC_OPTIONS='-v' '-O1' '-fipa-cp' '-Wall' '-c' '-o'
'fprintf-mini-bug-4.6.o' '-mtune=generic' '-march=i686'
 /usr/libexec/gcc/i686-pc-linux-gnu/4.5.3/cc1 -fpreprocessed
fprintf-mini-bug-4.6.i -quiet -dumpbase fprintf-mini-bug-4.6.i -mtune=generic
-march=i686 -auxbase-strip fprintf-mini-bug-4.6.o -O1 -Wall -version -fipa-cp
-o /tmp/ccAnJvmq.s
GNU C (Gentoo 4.5.3-r1 p1.0, pie-0.4.5) version 4.5.3 (i686-pc-linux-gnu)
    compiled by GNU C version 4.5.3, GMP version 5.0.2, MPFR version 3.0.1-p4,
MPC version 0.8.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C (Gentoo 4.5.3-r1 p1.0, pie-0.4.5) version 4.5.3 (i686-pc-linux-gnu)
    compiled by GNU C version 4.5.3, GMP version 5.0.2, MPFR version 3.0.1-p4,
MPC version 0.8.2
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 8436f5776e6fdb86b8b69daea94dff9c
fprintf-mini-bug-4.6.i: In function ‘write_cfg’:
fprintf-mini-bug-4.6.i:4:1: sorry, unimplemented: inlining failed in call to
‘foo’: originally indirect function call not considered for inlining
fprintf-mini-bug-4.6.i:11:7: sorry, unimplemented: called from here

This is with the code from comment 2 and '-fipa-cp'
 doesn't help in that case.

It does, however, for gcc 4.6.1.


  parent reply	other threads:[~2011-09-24 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-24 13:08 [Bug c/50506] New: " galtgendo at o2 dot pl
2011-09-24 13:18 ` [Bug c/50506] " galtgendo at o2 dot pl
2011-09-24 13:18 ` galtgendo at o2 dot pl
2011-09-24 13:46 ` galtgendo at o2 dot pl
2011-09-24 14:18 ` galtgendo at o2 dot pl [this message]
2011-09-24 16:05 ` pinskia at gcc dot gnu.org
2011-09-24 16:24 ` galtgendo at o2 dot pl
2011-09-25 12:27 ` rguenth at gcc dot gnu.org
2011-09-25 13:22 ` galtgendo at o2 dot pl
2011-09-25 13:58 ` galtgendo at o2 dot pl
2011-09-25 14:12 ` galtgendo at o2 dot pl
2011-09-25 17:20 ` rguenth at gcc dot gnu.org
2011-09-25 18:10 ` galtgendo at o2 dot pl

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-50506-4-d1byTGT3CQ@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).