public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/aoliva/heads/testme] (2 commits) Add TFLAGS to uses of GCC_FOR_TARGET in gnatlib Date: Thu, 19 May 2022 10:36:01 +0000 (GMT) [thread overview] Message-ID: <20220519103601.359D738515D9@sourceware.org> (raw) The branch 'aoliva/heads/testme' was updated to point to: 62309a3bae4... Add TFLAGS to uses of GCC_FOR_TARGET in gnatlib It previously pointed to: 637800859ad... Add TFLAGS to uses of GCC_FOR_TARGET in gnatlib Diff: !!! WARNING: THE FOLLOWING COMMITS ARE NO LONGER ACCESSIBLE (LOST): ------------------------------------------------------------------- 6378008... Add TFLAGS to uses of GCC_FOR_TARGET in gnatlib fbdfe12... Support multilib-aware target lib flags self-specs overridi Summary of changes (added commits): ----------------------------------- 62309a3... Add TFLAGS to uses of GCC_FOR_TARGET in gnatlib 7513dac... Support multilib-aware target lib flags self-specs overridi
next reply other threads:[~2022-05-19 10:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-19 10:36 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-05-19 10:15 Alexandre Oliva
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=20220519103601.359D738515D9@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).