grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Colin Watson <cjwatson@ubuntu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Need --divide flag for assembly of startup.S on some platforms
Date: Sat, 4 Dec 2010 15:47:53 +0000	[thread overview]
Message-ID: <20101204154752.GA21862@riva.ucam.org> (raw)
In-Reply-To: <4CF812B2.8080209@gmail.com>

On Thu, Dec 02, 2010 at 10:42:10PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 12/02/2010 10:29 PM, Colin Watson wrote:
> > On Thu, Dec 02, 2010 at 01:15:10PM -0800, Seth Goldberg wrote:
> >>   Since the default for gas on these platforms is to use he division 
> >> operator as a comment delimiter, the "-Wa,--divide" flags need to be 
> >> passed on the gcc command line when assembling such files.
> >
> > Can we just use >> 1 instead?
> 
> This was my first thought. But for maintenance reasons it would be
> better if we can make all platforms behave the same. Can we just
> inconditionally add -Wa,--divide to TARGET_ASFLAGS ?

(Only on i386, since the existence of the --divide option is
machine-dependent.)

It'd be a substantial bump in our binutils requirement.  Right now,
INSTALL says that we require GNU binutils 2.9.1.0.23 or later.  As far
as I can make out from
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gas/config/tc-i386.c?cvsroot=src,
--divide was added in binutils 2.17.  Before that, if I'm reading the
diff correctly, "/" unconditionally introduced a comment on certain
platforms.

So, is it better to require binutils 2.17, or to accept the maintenance
burden of avoiding the / operator in i386 assembly?  My instinct remains
the latter, I think - I have no idea what version of binutils is in
place on our various supported platforms, and I'm not even sure how to
go about finding out, so raising it is a bit scary for me.  I'm used to
platforms that stay pretty current on the GNU toolchain, but I know not
all platforms are like that.

-- 
Colin Watson                                       [cjwatson@ubuntu.com]


  reply	other threads:[~2010-12-04 15:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 15:51 BtrFS available in experimental Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-02 14:41 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-02 21:15   ` Need --divide flag for assembly of startup.S on some platforms Seth Goldberg
2010-12-02 21:29     ` Colin Watson
2010-12-02 21:39       ` Seth Goldberg
2010-12-03  0:53         ` Error building grub-emu (gnulib/progname.c) Seth Goldberg
2010-12-03  1:07           ` Seth Goldberg
2010-12-03  1:20             ` Seth Goldberg
2010-12-03  1:29             ` Another error building grub-emu (gnulib/error.c) Seth Goldberg
2010-12-03  1:39               ` Seth Goldberg
2010-12-02 21:42       ` Need --divide flag for assembly of startup.S on some platforms Vladimir 'φ-coder/phcoder' Serbinenko
2010-12-04 15:47         ` Colin Watson [this message]
2010-12-04 16:20           ` Colin Watson
2010-12-03 21:20     ` Need LARGEFILE_SOURCE && _FILE_OFFSET_BITS=64 Seth Goldberg
2010-12-04 15:25       ` Colin Watson
2010-12-06  7:18         ` Seth Goldberg
2010-12-03 21:02   ` BtrFS available in experimental Vladimir 'φ-coder/phcoder' Serbinenko

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=20101204154752.GA21862@riva.ucam.org \
    --to=cjwatson@ubuntu.com \
    --cc=grub-devel@gnu.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 NNTP newsgroup(s).