From: Andreas Jaeger <aj@suse.de>
To: Robert Love <rml@tech9.net>
Cc: Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@muc.de>,
akpm@osdl.org, rth@redhat.com, linux-kernel@vger.kernel.org,
jh@suse.cz
Subject: Re: [PATCH] Use -fno-unit-at-a-time if gcc supports it
Date: Fri, 05 Sep 2003 18:10:17 +0200 [thread overview]
Message-ID: <u8d6efmd1y.fsf@gromit.moeb> (raw)
In-Reply-To: <1062778587.8510.10.camel@boobies.awol.org> (Robert Love's message of "Fri, 05 Sep 2003 12:16:27 -0400")
[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]
Robert Love <rml@tech9.net> writes:
> On Fri, 2003-09-05 at 11:17, Andreas Jaeger wrote:
>
>
>> Since unit-at-a-time has better inlining heuristics the better way is
>> to add the used attribute - but that takes some time. The short-term
>> solution would be to add the compiler flag,
>
> Won't we get a linker error if a static symbol is used but
> optimized-away? It shouldn't be hard to fix the n linker errors that
> crop up.
Yes, we would get a linker error.
> And why are we using static symbols in inline assembly outside of the
> compilation scope?
Don't know.
> Anyhow, if it generates an error, this isn't hard to fix.
Just lots of places...
> Here is the start...
>
> Robert Love
>
>
> --- linux-rml/include/linux/compiler.h Fri Sep 5 11:57:56 2003
> +++ linux/include/linux/compiler.h Fri Sep 5 12:02:02 2003
> @@ -74,6 +74,19 @@
> #define __attribute_pure__ /* unimplemented */
> #endif
>
> +/*
> + * As of gcc 3.2, we can mark a function as 'used' and gcc will assume that,
> + * even if it does not find a reference to it in any compilation unit. We
> + * need this for gcc 3.4 and beyond, which can optimize on a program-wide
> + * scope, and not just one file at a time, to avoid static symbols being
> + * discarded.
> + */
> +#if (__GNUC__ == 3 && __GNUC_MINOR__ > 1) || __GNUC__ > 3
> +#define __attribute_used__ __attribute__((used))
> +#else
> +#define __attribute_used__ /* unimplemented */
In glibc we have for the else case:
# define __attribute_used__ __attribute__ ((__unused__))
This might reduce warnings about unused functions. But this change is
not critical IMO, so your patch looks fine!
> +#endif
> +
> /* This macro obfuscates arithmetic on a variable address so that gcc
> shouldn't recognize the original var, and make assumptions about it */
> #define RELOC_HIDE(ptr, off) \
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: 197 bytes --]
next prev parent reply other threads:[~2003-09-05 16:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 0:47 [PATCH] Use -fno-unit-at-a-time if gcc supports it Andi Kleen
2003-09-05 1:05 ` Aaron Lehmann
2003-09-05 1:24 ` Andi Kleen
2003-09-05 5:37 ` Jan Hubicka
2003-09-05 17:27 ` Andi Kleen
2003-09-05 17:59 ` Jeff Garzik
2003-09-06 7:08 ` Jan Hubicka
2003-09-05 14:54 ` Linus Torvalds
2003-09-05 15:17 ` Andreas Jaeger
2003-09-05 16:16 ` Robert Love
2003-09-05 16:10 ` Andreas Jaeger [this message]
2003-09-06 7:06 ` Jan Hubicka
2003-09-05 17:19 ` Jakub Jelinek
2003-09-05 17:30 ` Andi Kleen
2003-09-08 9:48 ` Helge Hafting
[not found] <sqnW.3zE.13@gated-at.bofh.it>
[not found] ` <sqHd.3Yj.1@gated-at.bofh.it>
[not found] ` <srtA.53H.1@gated-at.bofh.it>
[not found] ` <sFmW.78P.13@gated-at.bofh.it>
2003-09-06 8:10 ` David Mosberger-Tang
2003-09-08 20:32 ` David Mosberger
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=u8d6efmd1y.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jh@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=rth@redhat.com \
--cc=torvalds@osdl.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