public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: John David Anglin <danglin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-4941] Move PREFERRED_DEBUGGING_TYPE define in pa64-hpux.h to pa.h Date: Fri, 5 Nov 2021 15:05:46 +0000 (GMT) [thread overview] Message-ID: <20211105150546.6AC333858C27@sourceware.org> (raw) https://gcc.gnu.org/g:a505e1fae4378254275ec292bd5299a16357de90 commit r12-4941-ga505e1fae4378254275ec292bd5299a16357de90 Author: John David Anglin <danglin@gcc.gnu.org> Date: Fri Nov 5 15:05:15 2021 +0000 Move PREFERRED_DEBUGGING_TYPE define in pa64-hpux.h to pa.h This fixes D language build on hppa64-hpux11. 2021-11-05 John David Anglin <danglin@gcc.gnu.org> gcc/ChangeLog: * config/pa/pa.h (PREFERRED_DEBUGGING_TYPE): Define to DWARF2_DEBUG. * config/pa/pa64-hpux.h (PREFERRED_DEBUGGING_TYPE): Remove define. Diff: --- gcc/config/pa/pa.h | 3 +++ gcc/config/pa/pa64-hpux.h | 1 - 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/gcc/config/pa/pa.h b/gcc/config/pa/pa.h index 7a313d617b0..0fe3fd6796b 100644 --- a/gcc/config/pa/pa.h +++ b/gcc/config/pa/pa.h @@ -136,6 +136,9 @@ extern unsigned long total_code_bytes; by default. */ #define DEFAULT_GDB_EXTENSIONS 1 +/* Select dwarf2 as the preferred debug format. */ +#define PREFERRED_DEBUGGING_TYPE DWARF2_DEBUG + /* This used to be zero (no max length), but big enums and such can cause huge strings which killed gas. diff --git a/gcc/config/pa/pa64-hpux.h b/gcc/config/pa/pa64-hpux.h index c25bc38ba64..3ee97a418a2 100644 --- a/gcc/config/pa/pa64-hpux.h +++ b/gcc/config/pa/pa64-hpux.h @@ -266,7 +266,6 @@ do { \ /* It looks like DWARF2 will be the easiest debug format to handle on this platform. */ #define DWARF2_DEBUGGING_INFO 1 -#define PREFERRED_DEBUGGING_TYPE DWARF2_DEBUG /* This target uses the ELF object file format. */ #define OBJECT_FORMAT_ELF
reply other threads:[~2021-11-05 15:05 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=20211105150546.6AC333858C27@sourceware.org \ --to=danglin@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: linkBe 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).