public inbox for binutils-cvs@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] gas: avoid inserting extra newline in buffer_and_nest()
Date: Mon,  5 Dec 2022 12:53:10 +0000 (GMT)	[thread overview]
Message-ID: <20221205125310.C7C0F389942F@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=fde7a8e4b007a29c7196fd5b017342899c367c00

commit fde7a8e4b007a29c7196fd5b017342899c367c00
Author: Jan Beulich <jbeulich@suse.com>
Date:   Mon Dec 5 13:50:27 2022 +0100

    gas: avoid inserting extra newline in buffer_and_nest()
    
    In "-alm" listings I've noticed an odd blank line following the inserted
    .linefile one. This results from the explicit NL inserted being
    redundant with the one left in place from the original input line by all
    respective callers. Note that we need to compensate for the removed line
    by bumping the directive argument (which in turn is decremented again in
    s_linefile() before calling new_logical_line_flags(), and I have to
    confess that when putting together the original change I was a little
    puzzled by the imbalance of increments/decrements, but then I forgot to
    actually go look for the cause).
    
    While there also switch to sb_add_string() instead of effectively open-
    coding it to some degree.

Diff:
---
 gas/macro.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gas/macro.c b/gas/macro.c
index c2a47684b15..3d5774ee5e1 100644
--- a/gas/macro.c
+++ b/gas/macro.c
@@ -142,10 +142,10 @@ buffer_and_nest (const char *from, const char *to, sb *ptr,
 
       as_where (&line);
       if (!flag_m68k_mri)
-	linefile = xasprintf ("\t.linefile %u .\n", line);
+	linefile = xasprintf ("\t.linefile %u .", line + 1);
       else
-	linefile = xasprintf ("\tlinefile %u .\n", line);
-      sb_add_buffer (ptr, linefile, strlen (linefile));
+	linefile = xasprintf ("\tlinefile %u .", line + 1);
+      sb_add_string (ptr, linefile);
       xfree (linefile);
     }

                 reply	other threads:[~2022-12-05 12:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221205125310.C7C0F389942F@sourceware.org \
    --to=jbeulich@sourceware.org \
    --cc=bfd-cvs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).