public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dank at kegel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/14096] [3.5 Regression] [unit-at-a-time] verify_cgraph_node failed with always_inline
Date: Fri, 28 May 2004 02:01:00 -0000	[thread overview]
Message-ID: <20040527165455.21745.qmail@sourceware.org> (raw)
In-Reply-To: <20040210131810.14096.falk@debian.org>


------- Additional Comments From dank at kegel dot com  2004-05-27 16:54 -------
This happens when compiling glibc-2.3.2's stdlib/atof.c for i686 as well.

z.i:15: error: Inlined_to pointer is set but no predecesors found
strtod/3: (inline copy in atof/2) 14 insns tree always_inline
  called by: 
  calls: __strtod_internal/0 
z.i:15: internal compiler error: verify_cgraph_node failed.

To repeat:

i686-unknown-linux-gnu-gcc -O -c z.i

where z.i is:

extern double strtod(__const char *__restrict __nptr, char **__restrict __endptr);
extern double __strtod_internal(__const char *__restrict __nptr, char
**__restrict __endptr, int __group);
extern __inline double
strtod(__const char *__restrict __nptr, char **__restrict __endptr)
{
    return __strtod_internal(__nptr, __endptr, 0);
}
extern __inline double atof(__const char *__nptr)
{
    return strtod(__nptr, (char **) ((void *) 0));
}
double atof(const char *nptr)
{
    return strtod(nptr, (char **) ((void *) 0));
}


-- 


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


  parent reply	other threads:[~2004-05-27 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-10 13:18 [Bug optimization/14096] New: " falk at debian dot org
2004-02-10 15:59 ` [Bug optimization/14096] [tree-ssa] [unit-at-a-time] " pinskia at gcc dot gnu dot org
2004-03-04  1:22 ` rth at gcc dot gnu dot org
2004-05-05 21:59 ` hubicka at gcc dot gnu dot org
2004-05-21 21:57 ` [Bug tree-optimization/14096] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-05-28  2:01 ` dank at kegel dot com [this message]
2004-05-28  3:05 ` pinskia at gcc dot gnu dot org
2004-07-20  9:34 ` aoliva 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=20040527165455.21745.qmail@sourceware.org \
    --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).