From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001083] Fix warnings on creating target.ld for i386 targets
Date: Sat, 01 Jan 2011 19:18:00 -0000 [thread overview]
Message-ID: <20110101191813.40F232F78004@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001083-104@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001083
--- Comment #3 from Sergei Gavrikov <sergei.gavrikov@gmail.com> 2011-01-01 19:18:10 GMT ---
(In reply to comment #1)
> Sergei, your proposed change looks good to me. It matches the use of
> ACTUAL_CFLAGS in some other architectural HALs (arm, m68k, etc).
John, my check:
Have no issue:
$ grep target.ld -A3 hal/*/arch/current/cdl/hal_*cdl| grep
'$(ACTUAL_CFLAGS)'|cut -d- -f1
hal/arm/arch/current/cdl/hal_arm.cdl
hal/coldfire/arch/current/cdl/hal_coldfire.cdl
hal/m68k/arch/current/cdl/hal_m68k.cdl
hal/synth/arch/current/cdl/hal_synth.cdl
Expectant:
$ grep target.ld -A3 hal/*/arch/current/cdl/hal_*cdl| grep '$(CFLAGS)'|cut -d-
-f1
hal/cortexm/arch/current/cdl/hal_cortexm.cdl
hal/frv/arch/current/cdl/hal_frv.cdl
hal/i386/arch/current/cdl/hal_i386.cdl
hal/openrisc/arch/current/cdl/hal_openrisc.cdl
hal/powerpc/arch/current/cdl/hal_powerpc.cdl
hal/sh/arch/current/cdl/hal_sh.cdl
hal/sparc/arch/current/cdl/hal_sparc.cdl
hal/sparclite/arch/current/cdl/hal_sparclite.cdl
I was able to verify builds for next architectures: 'cortexm', 'powerpc' and
'sh' (I have no other toolchains).
Unfortunately, the compilers need substitution s/CFLAGS/ACTUAL_CFLAGS/ and in
other places for those archs, i.e. on preprocessing stages (where compilers
generate dependencies). There are more such places for 'powerpc' and 'sh'
(sh2, sh3, ...) archs. My workaround just decrements the compiler's claims
and does not calm builds there. Can I take risks and make all corrections
without the ability to test all?
It is safe for me is to apply the fix only for 'i386' and 'cortexm' archs.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-01-01 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 18:33 [Bug 1001083] New: " bugzilla-daemon
2011-01-01 11:43 ` [Bug 1001083] " bugzilla-daemon
2011-01-01 12:38 ` bugzilla-daemon
2011-01-01 19:18 ` bugzilla-daemon [this message]
2011-01-01 19:35 ` bugzilla-daemon
2011-01-02 1:09 ` bugzilla-daemon
2011-01-02 14:00 ` bugzilla-daemon
2011-01-04 18:55 ` bugzilla-daemon
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=20110101191813.40F232F78004@mail.ecoscentric.com \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).