public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/15700] [3.5 Regression] [unit-at-a-time] Inlining problem leads to miscompilation of glibc
Date: Sun, 30 May 2004 20:28:00 -0000 [thread overview]
Message-ID: <20040529184940.19535.qmail@sourceware.org> (raw)
In-Reply-To: <20040528071502.15700.aj@gcc.gnu.org>
------- Additional Comments From hubicka at ucw dot cz 2004-05-29 18:49 -------
Subject: Re: [3.5 Regression] [unit-at-a-time] Inlining problem leads to miscompilation of glibc
>
> ------- Additional Comments From belyshev at lubercy dot com 2004-05-29 17:57 -------
> I can confirm this bug on i686-pc-linux-gnu
The problem is obviously that GCC decides to not compile the function.
I am not quite sure whether GCC should conclude that every aliased
function is implicitly __attribute__ ((used)) or whether GCC should know
how to avoid emitting the alias.
The first one is easier to implement so if there are no complains, I
will do the first. But why glibc is renaming static symbol never used
by asm code at first place?
Honza
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15700
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15700
next prev parent reply other threads:[~2004-05-29 18:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 21:34 [Bug middle-end/15700] New: " aj at gcc dot gnu dot org
2004-05-28 21:34 ` [Bug middle-end/15700] " aj at gcc dot gnu dot org
2004-05-28 22:22 ` [Bug middle-end/15700] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-05-29 1:06 ` [Bug middle-end/15700] [3.5 Regression] [unit-at-a-time] " pinskia at gcc dot gnu dot org
2004-05-30 19:52 ` belyshev at lubercy dot com
2004-05-30 20:28 ` hubicka at ucw dot cz [this message]
2004-06-18 16:03 ` belyshev at lubercy dot com
2004-06-18 16:06 ` pinskia at gcc dot gnu dot org
2004-07-02 20:45 ` pinskia at gcc dot gnu dot org
2004-07-02 20:55 ` pinskia at gcc dot gnu dot org
2004-07-09 5:38 ` aoliva at gcc dot gnu dot org
2004-07-09 6:43 ` pinskia at gcc dot gnu dot org
2004-07-18 6:56 ` pinskia at gcc dot gnu dot org
2004-11-24 20:33 ` [Bug middle-end/15700] [4.0 " pinskia at gcc dot gnu dot org
2004-11-24 21:32 ` hjl at lucon dot org
2004-11-24 21:38 ` pinskia at gcc dot gnu dot org
2005-02-23 18:52 ` pinskia at gcc dot gnu dot org
2005-03-04 23:29 ` aoliva at gcc dot gnu dot org
2005-03-14 17:09 ` rth at gcc dot gnu dot org
2005-03-16 17:15 ` cvs-commit at gcc dot gnu dot org
2005-03-16 20:37 ` cvs-commit at gcc dot gnu dot org
2005-03-16 20:39 ` rth at gcc dot gnu dot org
2005-03-16 21:51 ` rth at gcc dot gnu dot org
2005-03-31 13:03 ` cvs-commit at gcc dot gnu dot org
2005-04-01 11:39 ` cvs-commit 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=20040529184940.19535.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).