public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/redhat/heads/gcc-8-branch)] bootstrap/87338 - gcc 8.2 fails to bootstrap on ia64
Date: Fri, 14 May 2021 14:55:31 +0000 (GMT)	[thread overview]
Message-ID: <20210514145531.95D773949F32@sourceware.org> (raw)

https://gcc.gnu.org/g:b0a54a549563313c931870c5ce45785f5119a780

commit b0a54a549563313c931870c5ce45785f5119a780
Author: James Clarke <jrtc27@jrtc27.com>
Date:   Fri Apr 30 10:11:17 2021 +0200

    bootstrap/87338 - gcc 8.2 fails to bootstrap on ia64
    
    This uses ASM_OUTPUT_DEBUG_LABEL instead of ASM_GENERATE_INTERNAL_LABEL
    and ASM_OUTPUT_LABEL.
    
    2019-05-21  James Clarke  <jrtc27@jrtc27.com>
    
            PR bootstrap/87338
            * dwarf2out.c (dwarf2out_inline_entry): Use ASM_OUTPUT_DEBUG_LABEL
            instead of ASM_GENERATE_INTERNAL_LABEL and ASM_OUTPUT_LABEL.
    
    (cherry picked from commit fe18e4e0845c1821ca51e0a12c284b24a2b60f3a)

Diff:
---
 gcc/dwarf2out.c | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 6227874b719..2a2673910ea 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -27657,11 +27657,8 @@ dwarf2out_inline_entry (tree block)
   if (cur_line_info_table)
     ied->view = cur_line_info_table->view;
 
-  char label[MAX_ARTIFICIAL_LABEL_BYTES];
-
-  ASM_GENERATE_INTERNAL_LABEL (label, BLOCK_INLINE_ENTRY_LABEL,
-			       BLOCK_NUMBER (block));
-  ASM_OUTPUT_LABEL (asm_out_file, label);
+  ASM_OUTPUT_DEBUG_LABEL (asm_out_file, BLOCK_INLINE_ENTRY_LABEL,
+			  BLOCK_NUMBER (block));
 }
 
 /* Called from finalize_size_functions for size functions so that their body


                 reply	other threads:[~2021-05-14 14:55 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=20210514145531.95D773949F32@sourceware.org \
    --to=jakub@gcc.gnu.org \
    --cc=gcc-cvs@gcc.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 read-only IMAP folder(s) and NNTP newsgroup(s).