This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

FW: generation of divxu opcode in h8300-hms

From: Andrew Haley <aph at cambridge dot redhat dot com>
To: "Sanjiv Kumar Gupta, Noida" <sanjivg at noida dot hcltech dot com>
Cc: gcc at gnu dot org
Date: Thu, 4 Jul 2002 12:18:11 +0100 (BST)
Subject: FW: generation of divxu opcode in h8300-hms
References: <E04CF3F88ACBD5119EFE00508BBB21210355F29A@exch-01.noida.hcltech.com>

Sanjiv Kumar Gupta, Noida writes:
 > 
 > 
 > -----Original Message-----
 > From: Sanjiv Kumar Gupta, Noida 
 > Sent: Tuesday, July 02, 2002 5:14 PM
 > To: gnuh8@gnuh8.org.uk
 > Subject: generation of divxu opcode
 > 
 > 
 > Hi,
 > 
 > I wonder why h8300-hms-gcc does not generate "divxu" opcode. it rather uses
 > a function call even for 16-bit/8-bit division. Any idea why such behaviour.

If you look at h8300.md you'll see this test in the code that gnerates
this insn:

TARGET_H8300H || TARGET_H8300S

So, they will only be generated if you  specify H8/S or H8/300H.

Andrew.

References:
- FW: generation of divxu opcode in h8300-hms
  - From: Sanjiv Kumar Gupta, Noida

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]