From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fxload: do not pass -g on Microblaze
Date: Tue, 16 May 2017 08:55:08 +0200 [thread overview]
Message-ID: <20170516085508.4e416332@free-electrons.com> (raw)
In-Reply-To: <871srp9x9f.fsf@dell.be.48ers.dk>
Hello,
On Tue, 16 May 2017 07:38:36 +0200, Peter Korsgaard wrote:
> > A possible alternate solution is to disable fxload on Microblaze
> > entirely. If you prefer this option, let me know, and I'll send a
> > different patch.
>
> I wouldn't mind just disabling fxload. I personally haven't seen any hw
> with the cypress 8051's needing fxload in the last 10 years or so, and
> there are no reverse dependencies.
OK, I'll send a patch disabling fxload entirely then.
> I see that the bug is very old :/ I wonder why we don't have a lot of
> other fallout from it - Is fxload really the only package passing -g or
> is the fxload source code so special that the bug only triggers there?
We don't seem to see it with other packages, so there must be something
special in fxload's code that triggers the bug. But I must say I
haven't looked too deeply, fixing Microblaze gcc issues is not really my
top priority.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-16 6:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 20:01 [Buildroot] [PATCH] fxload: do not pass -g on Microblaze Thomas Petazzoni
2017-05-16 5:38 ` Peter Korsgaard
2017-05-16 6:55 ` Thomas Petazzoni [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=20170516085508.4e416332@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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