From: Jeff Law <jeffreyalaw@gmail.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Always default to DWARF2_DEBUG if not specified, warn about deprecated STABS
Date: Sat, 23 Oct 2021 16:19:10 -0600 [thread overview]
Message-ID: <8e614401-9044-cf80-d3d8-ba36db1fbf48@gmail.com> (raw)
In-Reply-To: <20211023200005.xknhnzfa7eyny5zf@lug-owl.de>
On 10/23/2021 2:00 PM, Jan-Benedict Glaw wrote:
> Hi Richard,
>
> On Tue, 2021-09-21 16:25:19 +0200, Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> I have built all targets from contrib/config-list.mk to make sure we
>> don't run into the #error and the following makes the STABS usage
>> explicit for pdp11 and hppa with SOM.
> I'm running build tests based on config-list.mk as well and see a good
> number of targets failing, all about the same, ie. for moxie-elf:
That's odd. My moxie-elf (and all the others I test) aren't seeing this.
http://gcc.gnu.org/jenkins
Jeff
next prev parent reply other threads:[~2021-10-23 22:19 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 [this message]
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
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=8e614401-9044-cf80-d3d8-ba36db1fbf48@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=rguenther@suse.de \
/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).