public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: geoffk@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7515: invalid inlining
Date: Tue, 06 Aug 2002 21:26:00 -0000 [thread overview]
Message-ID: <20020807042601.24253.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/7515; it has been noted by GNATS.
From: Ulrich Drepper <drepper@redhat.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: optimization/7515: invalid inlining
Date: Tue, 06 Aug 2002 21:17:05 -0700
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Geoff Keating wrote:
> This is not a bug unless -fpic is used, since executables themselves
> will not have any symbols overriden, correct?
This assumes clueful programmers. Often code for DSO are compiled
without -fpic. Sometimes it gets forgotten. Other times people believe
the "PIC register prevents optimization" myth. The text relocations
DSOs and up with having often go completely unnoticed.
So, no, -fpic is no prerequisite for this being a bug.
- --
- ---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9UJ9H2ijCOnn/RHQRAiJwAKCgut+4fC4Zoq3VUC2a/knlBz/pRACggv8B
gg0/a/wOdwawFNE4IOxUseg=
=Mdrw
-----END PGP SIGNATURE-----
next reply other threads:[~2002-08-07 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 21:26 Ulrich Drepper [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-30 19:46 rth
2002-08-06 21:16 Geoff Keating
2002-08-06 21:10 geoffk
2002-08-06 20:26 drepper
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=20020807042601.24253.qmail@sources.redhat.com \
--to=drepper@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=geoffk@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).