public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/104861] s-oscons.ads should use target_noncanonical
Date: Thu, 10 Mar 2022 10:36:39 +0000 [thread overview]
Message-ID: <bug-104861-4-jDfFSIzd7D@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104861-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104861
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 10 Mar 2022, ebotcazou at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104861
>
> Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Ever confirmed|0 |1
> Last reconfirmed| |2022-03-10
> Status|UNCONFIRMED |NEW
> CC| |charlet at gcc dot gnu.org,
> | |ebotcazou at gcc dot gnu.org
>
> --- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Thanks for the investigation and the proposed patch.
Just as extra datapoint the patch makes s-oscons.ads consistent with
what gcc -dumpmachine says.
next prev parent reply other threads:[~2022-03-10 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 7:37 [Bug ada/104861] New: " rguenth at gcc dot gnu.org
2022-03-10 9:20 ` [Bug ada/104861] " ebotcazou at gcc dot gnu.org
2022-03-10 9:29 ` ebotcazou at gcc dot gnu.org
2022-03-10 10:36 ` rguenther at suse dot de [this message]
2022-03-10 10:39 ` charlet at gcc dot gnu.org
2022-03-10 12:40 ` cvs-commit at gcc dot gnu.org
2022-03-16 7:18 ` rguenth at gcc dot gnu.org
2022-03-16 8:22 ` cvs-commit at gcc dot gnu.org
2022-04-21 12:51 ` cvs-commit at gcc dot gnu.org
2022-04-21 12:58 ` rguenth at gcc dot gnu.org
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=bug-104861-4-jDfFSIzd7D@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).