public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/10320: [3.4 regression] gcc 3.4 gets rid of static inline function that does not get inlined
Date: Sun, 06 Apr 2003 17:26:00 -0000	[thread overview]
Message-ID: <20030406172600.20611.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/10320; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Andrew Pinski <pinskia@physics.uc.edu>, gcc-gnats@gcc.gnu.org
Subject: Re: c/10320: [3.4 regression] gcc 3.4 gets rid of static inline function that does not get inlined
Date: Sun, 6 Apr 2003 13:19:56 -0400

 This is not a bug report against ssa-branch but against 3.4 which has  
 the problem.
 And causing me not able to bootstrap with that compiler in the first  
 stage.
 There is another problem in the second stage for ssa-branch if I use  
 the `apple's 3.1 (1175)' as the first stage compiler which I will send  
 you about later.
 
 Thanks,
 Andrew Pinski
 
 On Sunday, Apr 6, 2003, at 13:13 US/Eastern, Diego Novillo wrote:
 
 > On Sun, 06 Apr 2003, pinskia@physics.uc.edu wrote:
 >
 >> compile and link and run (try at least) the following source:
 >> static inline void temp();
 >> int main()
 >> {
 >>         temp();
 >>         return 0;
 >> }
 >> static void temp(){}
 >>
 > Hmm, I can't reproduce this on ssa-branch (PPC/Linux):
 >
 > ----------------------------------------------------------------------- 
 > ------
 >  ./cc1 -fpreprocessed a.i -quiet -dumpbase a.c -auxbase a -O2 -version  
 > -o a.s
 > GNU C version 3.5-tree-ssa 20030302 (experimental)  
 > (powerpc-unknown-linux-gnu)
 >         compiled by GNU C version 3.5-tree-ssa 20030302 (experimental).
 > GGC heuristics: --param ggc-min-expand=38 --param  
 > ggc-min-heapsize=15614
 >  as --traditional-format -mppc -V -Qy -o a.o a.s
 > GNU assembler version 2.10.91 (ppc-yellowdog-linux) using BFD version  
 > 2.10.0.33
 >  ./collect2 -V -Qy -m elf32ppclinux -dynamic-linker /lib/ld.so.1 -o a  
 > /usr/lib/crt1.o /usr/lib/crti.o ./crtbegin.o -L.  
 > -L/home/dnovillo/clean-tree-ssa/native.ppc/lib/gcc-lib/powerpc- 
 > unknown-linux-gnu/3.5-tree-ssa  
 > -L/home/dnovillo/clean-tree-ssa/native.ppc/lib/gcc-lib/powerpc- 
 > unknown-linux-gnu/3.5-tree-ssa/../../.. a.o
 > -lgcc -lgcc_eh -lc -lgcc -lgcc_eh ./crtsavres.o ./crtend.o  
 > /usr/lib/crtn.o
 > GNU ld version 2.10.91 (with BFD 2.10.0.33)
 >   Supported emulations:
 >    elf32ppclinux
 >    elf32ppc
 >    elf32ppcsim
 > ----------------------------------------------------------------------- 
 > ------
 >
 > Can you send me the bootstrap failure message you get on Darwin?
 >
 >
 > Diego.
 >
 >
 


             reply	other threads:[~2003-04-06 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-06 17:26 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-15  5:31 bangerth
2003-04-06 17:16 Diego Novillo
2003-04-06 16:46 pinskia

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=20030406172600.20611.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).