public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Tony Breeds <tony@bakeyournoodle.com>
Cc: dhowells@redhat.com,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: triage for March 18, 2012
Date: Mon, 19 Mar 2012 15:21:31 +0000	[thread overview]
Message-ID: <9942.1332170491@redhat.com> (raw)
In-Reply-To: <1121.1332169437@redhat.com>


David Howells <dhowells@redhat.com> wrote:

> Tony Breeds <tony@bakeyournoodle.com> wrote:
> 
> > > 	frv:defconfig  (arch/frv/kernel/head.S operand out of range)
> 
> What binutils are you using?  I suspect this is fixed by a patch that only
> went upstream very recently.  Are you using a 64-bit machine to do your
> compilation?

Here's a patch I got from Nick Clifton to fix 64-bit binutils to handle
representing things like 0xfffffff1 as a 32-bit negative immediate argument.
It has been applied upstream.

David
---
Index: opcodes/cgen-asm.c
===================================================================
RCS file: /cvs/src/src/opcodes/cgen-asm.c,v
retrieving revision 1.14
diff -c -3 -p -r1.14 cgen-asm.c
*** opcodes/cgen-asm.c	2 Sep 2009 07:20:29 -0000	1.14
--- opcodes/cgen-asm.c	15 Dec 2011 08:27:02 -0000
*************** cgen_parse_signed_integer (CGEN_CPU_DESC
*** 268,274 ****
       &result, &value);
    /* FIXME: Examine `result'.  */
    if (!errmsg)
!     *valuep = value;
    return errmsg;
  }
  
--- 268,291 ----
       &result, &value);
    /* FIXME: Examine `result'.  */
    if (!errmsg)
!     {
! #if 1
!       /* Handle the case where a hex value is parsed on a 64-bit host.
! 	 A value like 0xffffe000 is clearly intended to be a negative
! 	 16-bit value, but on a 64-bit host it will be parsed by gas
! 	 as 0x00000000ffffe000.
! 
! 	 The shifts below are designed not to produce compile time
! 	 warnings when compiled on a 32-bit host.  */
!       if (sizeof (value) > 4
! 	  && result == CGEN_PARSE_OPERAND_RESULT_NUMBER
! 	  && value > 0
! 	  && (value & 0x80000000)
! 	  && ((value >> 31) == 1))
! 	value |= -1 << 31;
! #endif
!       *valuep = value;
!     }
    return errmsg;
  }
  
Index: opcodes/frv-asm.c
===================================================================
RCS file: /cvs/src/src/opcodes/frv-asm.c,v
retrieving revision 1.19
diff -c -3 -p -r1.19 frv-asm.c
*** opcodes/frv-asm.c	27 Jun 2010 04:07:55 -0000	1.19
--- opcodes/frv-asm.c	15 Dec 2011 08:27:02 -0000
*************** parse_uhi16 (CGEN_CPU_DESC cd,
*** 465,475 ****
  	  if (errmsg == NULL
  	      && result_type == CGEN_PARSE_OPERAND_RESULT_NUMBER)
  	    {
! 	      /* If bfd_vma is wider than 32 bits, but we have a sign-
! 		 or zero-extension, truncate it.  */
! 	      if (value >= - ((bfd_vma)1 << 31)
! 		  || value <= ((bfd_vma)1 << 31) - (bfd_vma)1)
  		value &= (((bfd_vma)1 << 16) << 16) - 1;
  	      value >>= 16;
  	    }
  	  *valuep = value;
--- 465,475 ----
  	  if (errmsg == NULL
  	      && result_type == CGEN_PARSE_OPERAND_RESULT_NUMBER)
  	    {
! 	      /* If value is wider than 32 bits then be
! 		 careful about how we extract bits 16-31.  */
! 	      if (sizeof (value) > 4)
  		value &= (((bfd_vma)1 << 16) << 16) - 1;
+ 
  	      value >>= 16;
  	    }
  	  *valuep = value;

  reply	other threads:[~2012-03-19 15:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18 18:41 linux-next: triage for March 18, 2012 Paul Gortmaker
2012-03-18 23:51 ` Tony Breeds
2012-03-19 14:51   ` Paul Gortmaker
2012-03-27 23:59     ` Tony Breeds
2012-03-28  0:08       ` Paul Gortmaker
2012-03-19 15:03   ` David Howells
2012-03-19 15:21     ` David Howells [this message]
2012-03-19 17:23       ` Valdis.Kletnieks
2012-03-19 19:41         ` David Howells
2012-03-19 21:56           ` Valdis.Kletnieks
2012-03-19 22:20     ` Tony Breeds

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=9942.1332170491@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=tony@bakeyournoodle.com \
    /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