Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Finalizing fix committed for "[PATCH] sim: make sure to include strsignal prototype"
Date: Sun, 25 Mar 2012 14:26:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1203251004220.31061@dair.pair.com> (raw)
In-Reply-To: <201203250354.34883.vapier@gentoo.org>

On Sun, 25 Mar 2012, Mike Frysinger wrote:
> On Sunday 25 March 2012 03:40:20 Mike Frysinger wrote:
> > the BFD64 logic in gas' expr.c is fairly light.  i'm not even sure it makes
> > sense to key off of BFD64 since this code doesn't use bfd for number
> > processing.  it's just deciding whether to automatically upgrade bignum's
> > into int64's.  i'll post a patch to just delete the BFD64 logic there and
> > see what people have to say.
>
> ok, digging a bit more, that isn't going to work.  the gas parsing logic is
> tied too closely to the bfd_vma type which is directly tied to the
> aforementioned configure flag.
>
> since the fact.s test already tests both values (full & truncated), and in
> reality the compiled code is the same for both (since gas does the
> truncation), i've commented out the test that is larger than 32bits.

For cris-elf there's a gas test I added (a loong time ago,
before 1.1) that I never pursued, one with IIRC a temporarily
overflowing expression; one of the temporaries truncated on
32-bit-bfd.  I xfailed the test (gas/cris/shexpr-1) which makes
it xpass on 64-bit-bfd. :/  Mea culpa.  Maybe the same bug maybe
slightly different, but the same 32-vs-64-bit-bfd basic reason.

It'd be nice to have gas PR's for whatever you can blame on gas
from the bfin sim tests.

brgds, H-P


  reply	other threads:[~2012-03-25 14:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  4:23 [PATCH] sim: make sure to include strsignal prototype Mike Frysinger
2012-03-23  4:35 ` Mike Frysinger
2012-03-23  5:24 ` Hans-Peter Nilsson
2012-03-23 15:43   ` Mike Frysinger
2012-03-23 22:12     ` Hans-Peter Nilsson
2012-03-23 22:43       ` Mike Frysinger
2012-03-24  5:34     ` Mike Frysinger
2012-03-24  4:12   ` Mike Frysinger
2012-03-24  5:53     ` Hans-Peter Nilsson
2012-03-24  6:12       ` Mike Frysinger
2012-03-24  6:49         ` Hans-Peter Nilsson
2012-03-24 18:18           ` Mike Frysinger
2012-03-24 10:55   ` Finalizing fix committed for "[PATCH] sim: make sure to include strsignal prototype" Hans-Peter Nilsson
2012-03-24 18:24     ` Mike Frysinger
2012-03-24 20:55       ` Hans-Peter Nilsson
2012-03-25  8:14         ` Mike Frysinger
2012-03-25 14:03           ` Hans-Peter Nilsson
2012-03-25  7:40       ` Mike Frysinger
2012-03-25  7:54         ` Mike Frysinger
2012-03-25 14:26           ` Hans-Peter Nilsson [this message]
2012-03-24  5:39 ` [PATCH] sim: make sure to include strsignal prototype Mike Frysinger

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=alpine.BSF.2.00.1203251004220.31061@dair.pair.com \
    --to=hp@bitrange.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.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