This is the mail archive of the gcc-patches@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]

RE: Suspected bug lshift_value (expmed.c) and its patch


Then come back to my orginal mail. 

I use gcc with -m32 to build my cross-compiler, it supports long long. 
My target is 64-bit. 
need_64bit_hwint is NOT set.

Is this combination allowed or not? 

Actually, my port is pretty clean. I don't have other issues apart from this one.
So this combination may not cause many troubles after all.

Bingfeng

> -----Original Message-----
> From: Michael Meissner [mailto:meissner@linux.vnet.ibm.com] 
> Sent: 19 March 2009 15:24
> To: Bingfeng Mei
> Cc: Dave Korn; Richard Guenther; Eric Botcazou; 
> gcc-patches@gcc.gnu.org
> Subject: Re: Suspected bug lshift_value (expmed.c) and its patch
> 
> On Thu, Mar 19, 2009 at 08:20:22AM -0700, Bingfeng Mei wrote:
> > But I just use x86-64_unknow-linux-gnu host with -m32. It 
> does support long long. Can I use it build a 64-bit target compiler? 
> > 
> > If no, I have to bite the bullet to support 64-bit host 
> (some legacy code in our port has trouble). 
> 
> Yes, since gcc does support long long.  The issue comes up if 
> you use some
> other compiler that does not support long long.
> 
> -- 
> Michael Meissner, IBM
> 4 Technology Place Drive, MS 2203A, Westford, MA, 01886, USA
> meissner@linux.vnet.ibm.com
> 
> 


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