From: Richard Biener <rguenther@suse.de>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org, dave.anglin@bell.net
Subject: Re: [PATCH] Obsolete hppa[12]*-*-hpux10* and hppa[12]*-*-hpux11*
Date: Mon, 20 Sep 2021 18:46:55 +0200 (CEST) [thread overview]
Message-ID: <n8939r1-n499-82on-prq1-70q9q6n93s6@fhfr.qr> (raw)
In-Reply-To: <qo3756-op59-11so-8116-354ro6o3psn@fhfr.qr>
On Mon, 20 Sep 2021, Richard Biener wrote:
> On Mon, 20 Sep 2021, Jeff Law wrote:
>
> >
> >
> > On 9/20/2021 1:00 AM, Richard Biener wrote:
> > > This obsoletes the 32bit hppa-hpux configurations which only support
> > > STABS as debuginfo format.
> > >
> > > As discussed, I'm going to push this (and a changes.html entry) when
> > > it was included in a bootstrap/regtest cycle.
> > >
> > > 2021-09-20 Richard Biener <rguenther@suse.de>
> > >
> > > gcc/
> > > * config.gcc: Obsolete hppa[12]*-*-hpux10* and hppa[12]*-*-hpux11*.
> > >
> > > contrib/
> > > * config-list.mk: --enable-obsolete for hppa2.0-hpux10.1 and
> > > hppa2.0-hpux11.9.
> > Is this marking hppa2.0w-hp-hpux11 as obsolete? That platform is using ELF &
> > DWARF.
>
> If so then that's by mistake - I had the impression that all 32bit
> hpux pa targets are STABS only, but that's from trying to decipher
> config.gcc and the comments from you and David ... maybe the
> matching pattern needs to be "split"?
Btw, I don't see any elfos.h in the hppa[12]*-*-hpux11* case in config.gcc
and it contains a warning that the target doesn't support DWARF. But yes,
that pattern matches hppa2.0-hpux11.9 and the hppa*64*-*-hpux11* pattern
doesn't - there's hppa64-hpux11.0 in config-list.mk that does though.
Richard.
> Can you maybe take care of any adjustments necessary? I've also
> edited changes.html already.
>
> Thanks,
> Richard.
>
> > jeff
> >
> >
> >
>
>
--
Richard Biener <rguenther@suse.de>
SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg,
Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2021-09-20 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 7:00 Richard Biener
2021-09-20 14:37 ` Jeff Law
2021-09-20 16:37 ` Richard Biener
2021-09-20 16:46 ` Richard Biener [this message]
2021-09-20 17:12 ` Jeff Law
2021-09-22 12:34 ` John David Anglin
2021-09-22 13:20 ` Richard Biener
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=n8939r1-n499-82on-prq1-70q9q6n93s6@fhfr.qr \
--to=rguenther@suse.de \
--cc=dave.anglin@bell.net \
--cc=gcc-patches@gcc.gnu.org \
--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).