From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] bfin: Disable -fstack-usage
Date: Wed, 12 Sep 2012 10:10:12 -0700 [thread overview]
Message-ID: <20120912171012.GF22207@bill-the-cat> (raw)
In-Reply-To: <201209120959.30864.marex@denx.de>
On Wed, Sep 12, 2012 at 09:59:30AM +0200, Marek Vasut wrote:
> Dear Mike Frysinger,
>
> > On Tue, Sep 11, 2012 at 3:08 PM, Marek Vasut wrote:
> > > The GCC does not support this on blackfin, disable it.
> >
> > err, no, you're probably using gcc-4.5.x which didn't support
> > -fstack-usage. that is not specific to Blackfin as gcc didn't add it
> > until 4.6.x.
>
> I actually used gentoo here, so it's really possible there is some crap going
> on.
>
> $ bfin-unknown-elf-gcc --version
> bfin-unknown-elf-gcc (crosstool-NG hg+default-ff167977b163) 4.6.3
> Copyright (C) 2011 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> > why doesn't the cc-option check work ?
>
> I dunno man, probably because it's supported but broken, see (there's lot more
> to this, I cut it down):
I believe it's a gcc "feature" not a bug. -fstack-usage emits a warning
on targets where it's not supported and cc-option doesn't catch that.
How about if you make cc-option call -Werror ?
--
Tom
prev parent reply other threads:[~2012-09-12 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 19:08 [U-Boot] [PATCH 1/2] bfin: Disable -fstack-usage Marek Vasut
2012-09-11 19:08 ` [U-Boot] [PATCH 2/2] bfin: Fix warning in bfin_mac Marek Vasut
2012-09-12 4:27 ` Mike Frysinger
2012-09-12 9:51 ` Marek Vasut
2012-09-12 14:32 ` Joe Hershberger
2012-09-12 16:18 ` Mike Frysinger
2012-09-12 4:27 ` [U-Boot] [PATCH 1/2] bfin: Disable -fstack-usage Mike Frysinger
2012-09-12 7:59 ` Marek Vasut
2012-09-12 17:10 ` Tom Rini [this message]
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=20120912171012.GF22207@bill-the-cat \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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