public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104713] gcc does not reject -march=i686 -fcf-protection Date: Mon, 28 Feb 2022 10:25:34 +0000 [thread overview] Message-ID: <bug-104713-4-iuucsOy3Q0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104713-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104713 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Is OLPC really still around? I thought it died when Google came out with their chrome books.
next prev parent reply other threads:[~2022-02-28 10:25 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-28 10:15 [Bug target/104713] New: " bunk at stusta dot de 2022-02-28 10:25 ` pinskia at gcc dot gnu.org [this message] 2022-02-28 10:36 ` [Bug target/104713] " bunk at stusta dot de 2022-02-28 11:02 ` jakub at gcc dot gnu.org 2022-02-28 11:42 ` bunk at stusta dot de 2023-03-20 8:42 ` jay+ggcc@jp-hosting.net 2023-03-20 9:01 ` bunk at stusta dot de 2023-03-20 11:20 ` jay+ggcc@jp-hosting.net 2023-03-23 16:37 ` jay+ggcc@jp-hosting.net 2023-03-24 10:15 ` jay+ggcc@jp-hosting.net 2023-05-16 11:48 ` jay+ggcc@jp-hosting.net
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-104713-4-iuucsOy3Q0@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: 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).