public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Neal Frager <neal.frager@amd.com>
To: <binutils@sourceware.org>
Cc: <ibai.erkiaga-elorza@amd.com>, <nagaraju.mekala@amd.com>,
	<mark.hatle@amd.com>, <sadanand.mutyala@amd.com>,
	<appa.rao.nali@amd.com>, <vidhumouli.hunsigida@amd.com>,
	<luca.ceresoli@bootlin.com>, Neal Frager <neal.frager@amd.com>
Subject: [PATCH v1 1/1] gas: expr: fix support .long 0U and .long 0u
Date: Wed, 27 Sep 2023 14:21:30 +0100	[thread overview]
Message-ID: <20230927132130.1604555-1-neal.frager@amd.com> (raw)

Fix support for .long 0U and .long 0u in GCC.

This patch has been tested for years of AMD Xilinx Yocto
releases as part of the following patch set:

https://github.com/Xilinx/meta-xilinx/tree/master/meta-microblaze/recipes-devtools/binutils/binutils

Signed-off-by: Neal Frager <neal.frager@amd.com>
---
 gas/expr.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/gas/expr.c b/gas/expr.c
index 204cfebc4c7..0d4e955b63a 100644
--- a/gas/expr.c
+++ b/gas/expr.c
@@ -824,6 +824,15 @@ operand (expressionS *expressionP, enum expr_mode mode)
 	      break;
 	    }
 	}
+      if ((*input_line_pointer == 'U') || (*input_line_pointer == 'u'))
+	{
+	  input_line_pointer--;
+
+	  integer_constant ((NUMBERS_WITH_SUFFIX || flag_m68k_mri)
+	                    ? 0 : 10,
+	                    expressionP);
+	  break;
+	}
       c = *input_line_pointer;
       switch (c)
 	{
-- 
2.25.1


             reply	other threads:[~2023-09-27 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 13:21 Neal Frager [this message]
2023-09-27 13:33 ` Jan Beulich
2023-09-28 19:27   ` Michael Eager
2023-10-01 16:22     ` Frager, Neal
2023-10-01 16:34       ` Michael Eager
2023-10-01 18:06         ` Frager, Neal
2023-10-16  9:18       ` Jan Beulich

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=20230927132130.1604555-1-neal.frager@amd.com \
    --to=neal.frager@amd.com \
    --cc=appa.rao.nali@amd.com \
    --cc=binutils@sourceware.org \
    --cc=ibai.erkiaga-elorza@amd.com \
    --cc=luca.ceresoli@bootlin.com \
    --cc=mark.hatle@amd.com \
    --cc=nagaraju.mekala@amd.com \
    --cc=sadanand.mutyala@amd.com \
    --cc=vidhumouli.hunsigida@amd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).