From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Weirdo gcc 4.3.x behaviour
Date: Mon, 22 Nov 2010 13:12:35 -0000 [thread overview]
Message-ID: <000201cb8a46$ee3f70f0$cabe52d0$@deacon@arm.com> (raw)
In-Reply-To: <20101121191148.GA12234@n2100.arm.linux.org.uk>
Hi Russell,
> Has anyone else seen weird behaviour from the gcc 4.3 branch?
>
> I've tried gcc-4.3.2 + patch and also gcc-4.3.5, both of which behave
> differently with this change in the kernel:
>
> (asm-generic/pgtable-nopud.h)
> static inline int pgd_none(pgd_t pgd) { return 0; }
> static inline int pgd_bad(pgd_t pgd) { return 0; }
> static inline int pgd_present(pgd_t pgd) { return 1; }
>
> and subsequently adding:
> +#define pgd_none(pgd) 0
> +#define pgd_bad(pgd) 0
> +#define pgd_present(pgd) 1
>
> This causes completely unrelated functions to be optimized differently,
> as can be seen via the bloat-o-meter:
[...]
If you mail me the smallest diff to the kernel which causes this to
happen along with the .s/.i files (gcc --save-temps) for the file that
is changing then I'll pass the information on to the compiler guys at
ARM.
Thanks,
Will
next prev parent reply other threads:[~2010-11-22 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 19:11 Weirdo gcc 4.3.x behaviour Russell King - ARM Linux
2010-11-22 12:16 ` Mikael Pettersson
2010-11-22 13:12 ` Will Deacon [this message]
2010-11-22 22:22 ` Joe Perches
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='000201cb8a46$ee3f70f0$cabe52d0$@deacon@arm.com' \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).