From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS
Date: Sun, 28 Aug 2022 15:32:53 -0600 [thread overview]
Message-ID: <1a195efa-f8f0-61b0-71b8-8d566fa5e9c2@gmail.com> (raw)
In-Reply-To: <20220828075030.sasynazl7hbg7ku4@lug-owl.de>
On 8/28/2022 1:50 AM, Jan-Benedict Glaw wrote:
> On Tue, 2021-09-21 16:25:19 +0200, Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> This makes defaults.h choose DWARF2_DEBUG if PREFERRED_DEBUGGING_TYPE
>> is not specified by the target and errors out if DWARF DWARF is not supported.
> While I think the pdp11 bits arreved, the rest did not (yet). Just
> checked my auto-builder logs. When building current HEAD as
>
> ../gcc/configure --prefix=... --enable-werror-always \
> --enable-languages=all --disable-gcov \
> --disable-shared --disable-threads --without-headers \
> --target=...
> make V=1 all-gcc
>
> ALL of these targets won't build right now:
> aarch64-elf
> aarch64-rtems
> alpha64-dec-vms
> alpha-dec-vms
> arm-eabi
> arm-rtems
> arm-symbianelf
> arm-uclinux_eabi
> bfin-elf
> bfin-rtems
> bfin-uclinux
> c6x-elf
> c6x-uclinux
> cris-elf
> fido-elf
> fr30-elf
> ft32-elf
> i686-elf
> i686-lynxos
> i686-nto-qnx
> i686-pc-msdosdjgpp
> i686-rtems
> i686-wrs-vxworks
> i686-wrs-vxworksae
> lm32-elf
> lm32-rtems
> lm32-uclinux
> m32c-elf
> m68k-elf
> m68k-rtems
> m68k-uclinux
> moxie-elf
> moxie-rtems
> moxie-uclinux
> powerpc-eabi
> powerpc-eabialtivec
> powerpc-eabisim
> powerpc-eabisimaltivec
> powerpc-ibm-aix7.1
> powerpc-ibm-aix7.2
> powerpcle-eabi
> powerpcle-eabisim
> powerpcle-elf
> powerpc-lynxos
> powerpc-rtems
> powerpc-wrs-vxworks
> powerpc-wrs-vxworksmils
> powerpc-xilinx-eabi
> ppc-elf
> s390x-ibm-tpf
> sh-elf
> sh-rtems
> sh-superh-elf
> sh-wrs-vxworks
> sparc64-elf
> sparc64-rtems
> sparc-elf
> sparc-leon-elf
> sparc-rtems
> sparc-wrs-vxworks
> visium-elf
> x86_64-elf --with-fpmath=sse
> x86_64-rtems
> xtensa-elf
Umm, most of those -elf targets do build. See:
http://law-sandy.freeddns.org:8080
Jeff
next prev parent reply other threads:[~2022-08-28 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 14:25 Richard Biener
2021-09-28 6:14 ` Richard Biener
2021-09-28 13:18 ` Koning, Paul
2021-10-15 8:23 ` Richard Biener
2021-10-23 20:00 ` Jan-Benedict Glaw
2021-10-23 22:19 ` Jeff Law
2021-10-24 6:36 ` Richard Biener
2021-10-24 7:20 ` Jan-Benedict Glaw
2021-10-25 8:25 ` Richard Biener
2021-10-26 1:28 ` Joseph Myers
2021-10-29 14:48 ` ibuclaw
2022-08-28 7:50 ` Jan-Benedict Glaw
2022-08-28 21:32 ` Jeff Law [this message]
2022-08-29 20:11 ` Jan-Benedict Glaw
2022-08-31 16:05 ` Jeff Law
2022-09-07 10:50 ` Jan-Benedict Glaw
2022-09-07 11:57 ` Richard Biener
-- strict thread matches above, loose matches on Subject: below --
2021-09-10 12:12 Richard Biener
2021-09-10 15:08 ` Michael Matz
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=1a195efa-f8f0-61b0-71b8-8d566fa5e9c2@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).