From: Richard Biener <rguenther@suse.de>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
gcc-patches@gcc.gnu.org, dj@delorie.com
Subject: Re: [PATCH] Remove dbx.h, do not set PREFERRED_DEBUGGING_TYPE from dbxcoff.h, lynx.h
Date: Mon, 13 Sep 2021 11:28:15 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2109131126260.11781@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20210913035102.gxz6abkuo3cwhpte@lug-owl.de>
On Mon, 13 Sep 2021, Jan-Benedict Glaw wrote:
> Hi Richard,
>
> On Fri, 2021-09-10 08:02:00 +0200, Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> > > On 9/9/2021 7:19 AM, Richard Biener via Gcc-patches wrote:
> > > > The patch also removes the PREFERRED_DEBUGGING_TYPE define from
> > > > lynx.h which always follows elfos.h already defaulting to DWARF,
> > > > so the comment about STABS being the default is misleading and
> > > > outdated. There's no listed maintainer for Lynx OS.
> > > >
> > > > I have not tested this in any ways but I also have no idea how
> > > > to meaningfully do so.
>
> I'm not actually running such a configuration and cannot properly test
> it, but automated mass-building broke for --target=i686-lynxos:
Ah, I didn't spot
/* Undefine the definition from elfos.h to enable our default. */
#undef PREFERRED_DEBUGGING_TYPE
will fix.
Richard.
next prev parent reply other threads:[~2021-09-13 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 13:19 Richard Biener
2021-09-09 14:25 ` Jonathan Yong
2021-09-09 15:26 ` Jeff Law
2021-09-10 6:02 ` Richard Biener
2021-09-13 3:51 ` Jan-Benedict Glaw
2021-09-13 9:28 ` Richard Biener [this message]
2021-09-09 16:11 ` Jason Merrill
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=nycvar.YFH.7.76.2109131126260.11781@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=dj@delorie.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbglaw@lug-owl.de \
--cc=jeffreyalaw@gmail.com \
/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).