From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] usb: use noinline define
Date: Thu, 5 Apr 2012 16:35:43 -0400 [thread overview]
Message-ID: <201204051635.44443.vapier@gentoo.org> (raw)
In-Reply-To: <201204052224.14831.marek.vasut@gmail.com>
On Thursday 05 April 2012 16:24:14 Marek Vasut wrote:
> Dear Mike Frysinger,
> > On Thursday 05 April 2012 15:19:11 Marek Vasut wrote:
> > > Dear Mike Frysinger,
> > > > On Thursday 05 April 2012 06:13:21 Marek Vasut wrote:
> > > > > Dear Mike Frysinger,
> > > > > > Building usb for Blackfin boards fails as we get linux/compiler.h
> > > > > > included which expands the "noinline" inside of the attribute and
> > > > > > we get attribute(attribute(noinline)).
> > > > > >
> > > > > > Explicitly use the helper define to avoid this.
> > > > >
> > > > > Ain't compiler.h broken then?
> > > >
> > > > no ... why would it be ?
> > >
> > > Because it colides with gcc stuff?
> >
> > it provides shortcuts so you don't have to go grubbing into __attribute__
> > syntax, and it does so in a way that supports multiple gcc versions and
> > compilers (although the latter isn't generally a realistic use case for
> > us).
>
> U-Boot/LLVM or U-Boot/VC ? ;-)
>
> We'll have to support LLVM eventually anyway.
true ... people want to use llvm/clang for some reason (who cares about code
generation!?). linux/compiler.h will make that much easier for us.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120405/6044bcec/attachment.pgp>
prev parent reply other threads:[~2012-04-05 20:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 4:44 [U-Boot] [PATCH] usb: use noinline define Mike Frysinger
2012-04-05 10:13 ` Marek Vasut
2012-04-05 17:42 ` Mike Frysinger
2012-04-05 19:19 ` Marek Vasut
2012-04-05 19:29 ` Mike Frysinger
2012-04-05 20:24 ` Marek Vasut
2012-04-05 20:35 ` Mike Frysinger [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=201204051635.44443.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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