From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: unit-at-a-time fixes
Date: Sun, 30 Nov 2003 20:11:00 -0000 [thread overview]
Message-ID: <u8oeut4p7l.fsf@gromit.moeb> (raw)
In-Reply-To: <u8wu9h4pg4.fsf@gromit.moeb> (Andreas Jaeger's message of "Sun, 30 Nov 2003 20:38:19 +0100")
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
Andreas Jaeger <aj@suse.de> writes:
> With GCC 3.4 and also the hammer-branch of GCC 3.3, unit-at-a-time
> compilation is enabled and rearranges the output order of functions.
> This is not desirable in some cases.
>
> Here's the patch that we're currently using at SuSE. Ok to commit?
>
> Andreas
>
> 2003-11-30 Andreas Jaeger <aj@suse.de>
>
> * csu/Makefile (CFLAGS-initfini.s): Add -fno-unit-at-a-time.
> * linuxthreads/sysdeps/unix/sysv/linux/x86_64/Makefile
> (CFLAGS-pt-initfini.s): Likewise.
> * locale/Makefile (CFLAGS-loadlocale.c): Likewise.
There're two entries missing:
>
> For linuxthreads:
> * Makefile (CFLAGS-tst-cancel.c): Add -fno-unit-at-a-time.
> (CFLAGS-pt-initfini.s): Likewise.
* sysdeps/unix/sysv/linux/x86_64/Makefile (CFLAGS-pt-initfini.s):
Likewise.
> For nptl:
> * Makefile (CFLAGS-pt-initfini.s): Add -fno-unit-at-a-time.
* sysdeps/unix/sysv/linux/x86_64/Makefile (CFLAGS-pt-initfini.s):
Likewise.
Andreas
--
Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj
SuSE Linux AG, Deutschherrnstr. 15-19, 90429 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-11-30 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 19:43 Andreas Jaeger
2003-11-30 20:11 ` Andreas Jaeger [this message]
2003-11-30 20:50 ` Jakub Jelinek
2003-11-30 21:43 ` Andreas Jaeger
[not found] ` <u8u14l352k.fsf@gromit.moeb>
2003-12-01 10:07 ` Andreas Schwab
2003-12-01 16:57 ` Andreas Jaeger
2003-12-02 6:41 ` Ulrich 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=u8oeut4p7l.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
/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).