bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/4572] division doesn't work on solaris/x86


From: viskovatoff at imap dot cc
Subject: [Bug gas/4572] division doesn't work on solaris/x86
Date: 1 Aug 2009 17:13:52 -0000

------- Additional Comments From viskovatoff at imap dot cc  2009-08-01 17:13 
-------
Subject: Re:  division doesn't work on solaris/x86

hjl dot tools at gmail dot com wrote:
> ------- Additional Comments From hjl dot tools at gmail dot com  2009-08-01 
> 05:03 -------
> I suggest you add a new option to treate '/' as divide on Solaris.

Such an option already exists. It's called "--divide", and it was 
mentioned in earlier comments, including my own.

The reason I am proposing my patch is that it doesn't make any sense for 
GAS to observe the Solaris assembler reference manual stipulation that 
slashes begin comments, because if someone is interested in writing or 
using code directed specifically at Solaris, he or she will use the Sun 
assembler, not GAS. The reason people in the Solaris world use GAS is to 
port GNU/Linux programs, and making the behavior with respect to slashes 
specified in the Solaris assembler reference manual the default, as 
opposed to the behavior under Linux, makes that more difficult.

The question is: are we going to have people porting software from 
GNU/Linux to Solaris endlessly patch code to make GAS behave for 
Solaris/X86 targets as it does for Linux targets? Or are we going to 
make a single patch to GAS with the functionality proposed here, solving 
this problem once and for all?

People in the OpenSolaris community, unless they do a fair amount of 
Googling, usually conclude that this behavior of GAS for Solaris/X86 
targets is a bug when they run into it. Those who look into the problem 
a little more thoroughly optimistically expect that this behavior will 
go away with some future version of Binutils.

Alex


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4572

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]