public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/106855] [13 Regression] Removal of stabs/xcoff debugging broke bootstrap on AIX
Date: Wed, 07 Sep 2022 12:18:19 +0000	[thread overview]
Message-ID: <bug-106855-4-Gbdkjj2qds@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106855-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106855

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:7abcdb06e31d82d4933cb6e0a626c3ccb28fa0c3

commit r13-2519-g7abcdb06e31d82d4933cb6e0a626c3ccb28fa0c3
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Sep 7 11:47:40 2022 +0200

    Restore XCOFF for DWARF on AIX.

            PR bootstrap/106855

    gcc/ChangeLog:

            * collect2.cc (scan_prog_file): Restore if XCOFF_DEBUGGING_INFO.
            * config/rs6000/rs6000.cc (rs6000_option_override_internal):
              Restore usage of XCOFF_DEBUGGING_INFO.
            * config/rs6000/xcoff.h (XCOFF_DEBUGGING_INFO): Restore.
            * dwarf2asm.cc (XCOFF_DEBUGGING_INFO): Restore support for
              XCOFF_DEBUGGING_INFO.
            (dw2_asm_output_nstring): Likewise.
            (USE_LINKONCE_INDIRECT): Likewise.
            * dwarf2out.cc (XCOFF_DEBUGGING_INFO): Likewise.
            (HAVE_XCOFF_DWARF_EXTRAS): Likewise.
            (output_fde): Likewise.
            (output_call_frame_info): Likewise.
            (have_macinfo): Likewise.
            (add_AT_loc_list): Likewise.
            (add_AT_view_list): Likewise.
            (output_compilation_unit_header): Likewise.
            (output_pubnames): Likewise.
            (output_aranges): Likewise.
            (output_line_info): Likewise.
            (output_macinfo): Likewise.
            (dwarf2out_finish): Likewise.
            (dwarf2out_early_finish): Likewise.

  parent reply	other threads:[~2022-09-07 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 16:33 [Bug bootstrap/106855] New: " dje at gcc dot gnu.org
2022-09-06 16:33 ` [Bug bootstrap/106855] " dje at gcc dot gnu.org
2022-09-06 16:35 ` dje at gcc dot gnu.org
2022-09-07  8:25 ` rguenth at gcc dot gnu.org
2022-09-07 10:02 ` marxin at gcc dot gnu.org
2022-09-07 10:02 ` marxin at gcc dot gnu.org
2022-09-07 11:47 ` marxin at gcc dot gnu.org
2022-09-07 12:18 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-07 12:19 ` marxin at gcc dot gnu.org

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=bug-106855-4-Gbdkjj2qds@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).