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/108678] Windows on ARM64 platform target aarch64-w64-mingw32 Date: Sun, 05 Feb 2023 17:39:59 +0000 [thread overview] Message-ID: <bug-108678-4-fSNpydOU4r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=87334 Target| |Aarch64-mingw
next prev parent reply other threads:[~2023-02-05 17:39 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-05 14:43 [Bug c/108678] New: " brechtsanders at users dot sourceforge.net 2023-02-05 17:39 ` pinskia at gcc dot gnu.org [this message] 2023-02-05 18:19 ` [Bug target/108678] " pinskia at gcc dot gnu.org 2023-02-05 19:23 ` brechtsanders at users dot sourceforge.net 2023-06-24 20:14 ` brechtsanders at users dot sourceforge.net 2023-06-26 8:25 ` zac.walker at linaro dot org 2023-06-26 18:05 ` brechtsanders at users dot sourceforge.net 2023-06-26 20:34 ` zac.walker at linaro dot org 2023-06-26 22:05 ` redi at gcc dot gnu.org 2023-06-28 11:40 ` zac.walker at linaro dot org 2023-11-09 3:47 ` pinskia at gcc dot gnu.org 2024-04-17 20:15 ` brechtsanders at users dot sourceforge.net 2024-04-17 20:20 ` pinskia at gcc dot gnu.org 2024-04-18 9:14 ` clyon at gcc dot gnu.org 2024-05-14 8:08 ` unlvsur at live dot com 2024-05-14 9:56 ` unlvsur at live dot com 2024-06-05 13:39 ` Evgeny.Karpov at microsoft dot com
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-108678-4-fSNpydOU4r@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).