public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com
Subject: Re: ppc-gas: Add '+' and '-' to symbol chars list
Date: Thu, 24 Apr 2003 17:03:00 -0000	[thread overview]
Message-ID: <m3llxzsuco.fsf@localhost.localdomain> (raw)
In-Reply-To: <20030424081519.B7144@lucon.org>

Hi H.J.

> Would you mind adding a testcase for that? "make check" passed for
> me on pcc-linux.


Good idea.  Applying the patch below.

Cheers
        Nick

2003-04-24  Nick Clifton  <nickc@redhat.com>

	* gas/ppc/astest2.s: Add tests for conditional branches with
	probability indicators.
	* gas/ppc/astest2.d: Add expected disassembly.

Index: gas/testsuite/gas/ppc/astest2.s
===================================================================
RCS file: /cvs/src/src/gas/testsuite/gas/ppc/astest2.s,v
retrieving revision 1.1.1.1
diff -c -3 -p -w -r1.1.1.1 astest2.s
*** gas/testsuite/gas/ppc/astest2.s	3 May 1999 07:28:52 -0000	1.1.1.1
--- gas/testsuite/gas/ppc/astest2.s	24 Apr 2003 17:01:20 -0000
*************** y:	.long 0
*** 50,52 ****
--- 50,67 ----
  	.type	a,@function
  	.type	b,@function
  	.type	apfour,@function
+ 
+ 	.section ".text"
+ .L1:
+ 	nop
+ 	ble- 1,.L1
+ 	bgt- 2,.L1
+ 	ble+ 3,.L1
+ 	bgt+ 4,.L1
+ 	ble- 5,.L2
+ 	bgt- 6,.L2
+ 	ble+ 7,.L2
+ 	bgt+ 0,.L2
+ .L2:
+ 	nop:	
+ 

Index: gas/testsuite/gas/ppc/astest2.d
===================================================================
RCS file: /cvs/src/src/gas/testsuite/gas/ppc/astest2.d,v
retrieving revision 1.2
diff -c -3 -p -w -r1.2 astest2.d
*** gas/testsuite/gas/ppc/astest2.d	22 Aug 2002 05:23:43 -0000	1.2
--- gas/testsuite/gas/ppc/astest2.d	24 Apr 2003 17:01:20 -0000
*************** Disassembly of section \.text:
*** 66,71 ****
--- 66,80 ----
    88:	00 00 00 02 	\.long 0x2
  			88: R_PPC_ADDR32	apfour\+0x2
    8c:	00 00 00 00 	\.long 0x0
+   90:	60 00 00 00 	nop
+   94:	40 a5 ff fc 	ble-	cr1,90 <apfour\+0x14>
+   98:	41 a9 ff f8 	bgt-	cr2,90 <apfour\+0x14>
+   9c:	40 8d ff f4 	ble\+	cr3,90 <apfour\+0x14>
+   a0:	41 91 ff f0 	bgt\+	cr4,90 <apfour\+0x14>
+   a4:	40 95 00 10 	ble-	cr5,b4 <nop>
+   a8:	41 99 00 0c 	bgt-	cr6,b4 <nop>
+   ac:	40 bd 00 08 	ble\+	cr7,b4 <nop>
+   b0:	41 a1 00 04 	bgt\+	b4 <nop>
  Disassembly of section \.data:
  
  0+0000000 <x>:

  reply	other threads:[~2003-04-24 17:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24 10:21 Nick Clifton
2003-04-24 15:15 ` H. J. Lu
2003-04-24 17:03   ` Nick Clifton [this message]
2003-04-24 23:16 ` Alan Modra
2003-04-27 23:44 ` Alan Modra
2003-04-28  4:24   ` H. J. Lu
2003-04-28  8:35     ` Nick Clifton
2003-04-29  5:30       ` Alan Modra
2003-04-29 11:55         ` Nick Clifton
2003-04-29 16:06           ` H. J. Lu
2003-04-29 23:33             ` Alan Modra
2003-04-30  0:39               ` Daniel Jacobowitz
2003-04-30  4:55                 ` H. J. Lu
2003-04-30  8:46                   ` Alan Modra
2003-04-30  8:51                 ` Nick Clifton

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=m3llxzsuco.fsf@localhost.localdomain \
    --to=nickc@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=hjl@lucon.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).