public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@desire.geoffk.org>
To: amodra@bigpond.net.au
Cc: ksp@securelogix.com, dje@watson.ibm.com,
	binutils@sources.redhat.com, bug-binutils@gnu.org
Subject: Re: Powerpc Linux build fails
Date: Wed, 19 May 2004 04:27:00 -0000	[thread overview]
Message-ID: <200405190427.i4J4RYiU027950@desire.geoffk.org> (raw)
In-Reply-To: <20040519033008.GC12690@bubble.modra.org> (message from Alan Modra on Wed, 19 May 2004 13:00:08 +0930)

> Date: Wed, 19 May 2004 13:00:08 +0930
> From: Alan Modra <amodra@bigpond.net.au>

> On Tue, May 18, 2004 at 11:06:00AM -0500, Keith Pickens wrote:
> > 
> > Sorry, I wasn't saying the change was wrong but rather that it
> > has a side effect that broke builds that have worked for a
> > long time.
> [snip]
> 
> You're correct.  You're also using the correct -mcpu option to enable
> AltiVec.  The trouble is that gcc doesn't pass -maltivec or -m7400 on to
> gas, but instead just passes -mppc.  See gcc/config/rs6000/rs6000.h
> ASM_CPU_SPEC.  Fixing gcc to pass the right options is probably the
> right thing to do, but in the meantime we have released versions of
> gcc that should work with newer binutils.  I'm inclined to make gas
> behave as if -many was given, ie. accept any recognizable powerpc
> instruction.
> 
> Geoff, what do you think?

Certainly, -many should really accept every instruction, failure to do
that is just a bug.

I am not sure about this new -mstrict.  I am sure someone is expecting
-mpower3 to really mean 'power3 only' and will get a nasty surprise
when they use a power4 instruction by mistake and their program
crashes.

It is perfectly acceptable to say "GAS version X will only work with
GCC version > Y".  People using old GCC can always use old binutils
with it.  (They can also hack their specs file to pass -many, if
that's what they really want.)

The fully-correct way to do this is to have GCC generate a directive
after option parsing, like '.machine 7400' or so, and have GAS
interpret it, otherwise you end up in specs hell.  (Doesn't ppc gas
already have a directive like that?  I seem to remember seeing such a
patch fly by...)

> opcodes/ChangeLog
> 	* ppc-opc.c (insert_fxm): Enable two operand mfcr when -many as
> 	well as when -mpower4.
> gas/ChangeLog
> 	* config/tc-ppc.c (parse_cpu): Set PPC_OPCODE_ANY on all valid
> 	options besides a new -mstrict option.
> 	(md_show_usage): Update.  Correct capitalization.
> 	(ppc_arch): Expand comment.
> 	* doc/c-ppc.texi (PowerPC-Opts): Update.

-- 
- Geoffrey Keating <geoffk@geoffk.org>

  reply	other threads:[~2004-05-19  4:27 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A3FC75F7C72D711A7DC009027AC9C4B1788D9@jupiter>
2004-05-19  3:30 ` Alan Modra
2004-05-19  4:27   ` Geoff Keating [this message]
2004-05-19  5:10     ` Alan Modra
2004-05-19 16:24       ` Kumar Gala
2004-05-20  0:44         ` Alan Modra
     [not found] <44D2755E.9020600@us.ibm.com>
2006-08-04  1:30 ` Link problems with section anchors Alan Modra
2006-08-04  9:04   ` Richard Sandiford
2006-08-04 13:53     ` Steven Munroe
2006-08-04 13:54     ` David Edelsohn
2006-08-04 14:01       ` Richard Sandiford
2006-08-04 14:12         ` David Edelsohn
     [not found] <087e01c3b5da$77d658e0$0202040a@catdog>
2003-11-29  1:42 ` ppc problem with .rodata.str1.4. binutils requirement for gcc 3.3.1? Alan Modra
2003-11-29 18:14   ` Kris Warkentin
2001-12-31 19:09 Compiling kernel 2.4.17 fails at link stage Krishnakumar B
2002-01-04  3:50 ` Alan Modra
2002-01-04 12:39   ` [Linux-ia64] " Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2001-10-24 18:26 Release 2.12 Hans-Peter Nilsson
2001-10-24 18:38 ` Alan Modra
2001-10-24 18:43   ` David O'Brien
2001-10-24 19:30     ` Alan Modra
2001-10-24 19:35       ` MMIX (was: Re: Release 2.12) Hans-Peter Nilsson
2001-10-24 21:45       ` Release 2.12 Eric Christopher
2001-10-25  8:41         ` H . J . Lu
2001-10-25  8:47       ` H . J . Lu
2001-10-24 18:49   ` Daniel Jacobowitz
2001-10-24 19:43     ` Alan Modra
2001-10-24 20:10       ` Daniel Jacobowitz
2001-10-24 20:35         ` Alan Modra
2001-10-24 20:44           ` Daniel Jacobowitz
2001-10-25  5:09         ` Christopher C. Chimelis
2001-10-25  1:56       ` Philip Blundell
2001-10-25  8:30         ` H . J . Lu
2001-10-25  8:47           ` David O'Brien
     [not found]       ` <amodra@bigpond.net.au>
2002-01-04 17:42         ` [Linux-ia64] Compiling kernel 2.4.17 fails at link stage Grant Grundler
2002-01-04 17:59           ` H . J . Lu
2002-01-04 20:37             ` Grant Grundler
2002-01-04 22:39               ` H . J . Lu
2002-01-07 12:52                 ` Grant Grundler
2002-01-04 19:21           ` Alan Modra
2003-11-29  2:33         ` ppc problem with .rodata.str1.4. binutils requirement for gcc 3.3.1? David Edelsohn
2003-11-29  3:05           ` Alan Modra
2003-11-29  4:06         ` David Edelsohn
2003-11-29  4:10           ` Andrew Pinski
2003-11-29  4:20             ` David Edelsohn
2003-11-29  6:47               ` Alan Modra
2003-11-29 19:40         ` David Edelsohn
2004-05-19 15:19         ` Powerpc Linux build fails David Edelsohn
2004-05-20  0:39           ` Alan Modra
2004-05-20  1:24             ` Alan Modra
2004-05-20  1:46               ` Alan Modra
2004-05-20  2:29         ` David Edelsohn
2004-05-20  3:10           ` Alan Modra
2006-08-04  1:49         ` Link problems with section anchors David Edelsohn
2006-08-04  2:04           ` Alan Modra
2001-10-24 19:37   ` Release 2.12 Russ Allbery
2001-10-24 19:52     ` Alan Modra
2001-10-25  0:46 ` H . J . Lu
2001-10-25  8:57   ` David O'Brien
2001-10-25  9:38     ` H . J . Lu
2001-10-25  9:44       ` H . J . Lu

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=200405190427.i4J4RYiU027950@desire.geoffk.org \
    --to=geoffk@desire.geoffk.org \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=bug-binutils@gnu.org \
    --cc=dje@watson.ibm.com \
    --cc=ksp@securelogix.com \
    /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).