public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/92729] [avr] Convert the backend to MODE_CC so it can be kept in future releases Date: Fri, 22 May 2020 08:44:41 +0000 [thread overview] Message-ID: <bug-92729-4-1F1Uf9vuQy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-92729-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729 --- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> --- See also https://gcc.gnu.org/pipermail/gcc/2020-April/thread.html#402 (for details/current status, ask those involved).
next prev parent reply other threads:[~2020-05-22 8:44 UTC|newest] Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-92729-4@http.gcc.gnu.org/bugzilla/> 2020-05-22 4:53 ` f.mach4 at gmail dot com 2020-05-22 6:26 ` glaubitz at physik dot fu-berlin.de 2020-05-22 8:44 ` burnus at gcc dot gnu.org [this message] 2020-07-29 23:16 ` pipcet at gmail dot com 2020-08-04 16:54 ` pipcet at gmail dot com 2020-08-06 22:40 ` glaubitz at physik dot fu-berlin.de 2020-10-09 15:54 ` redi at gcc dot gnu.org 2020-11-10 16:38 ` abebeos at lazaridis dot com 2020-11-10 16:45 ` glaubitz at physik dot fu-berlin.de 2020-11-11 13:57 ` abebeos at lazaridis dot com 2020-11-14 20:23 ` gjl at gcc dot gnu.org 2020-11-15 13:27 ` gjl at gcc dot gnu.org 2020-11-15 14:13 ` abebeos at lazaridis dot com 2020-11-15 17:39 ` gjl at gcc dot gnu.org 2020-11-18 20:08 ` abebeos at lazaridis dot com 2020-11-29 0:10 ` abebeos at lazaridis dot com 2020-11-29 9:18 ` pipcet at gmail dot com 2020-11-29 10:54 ` abebeos at lazaridis dot com 2020-11-30 13:48 ` abebeos at lazaridis dot com 2020-11-30 13:54 ` saaadhu at gcc dot gnu.org 2020-11-30 13:57 ` glaubitz at physik dot fu-berlin.de 2020-11-30 14:14 ` abebeos at lazaridis dot com 2020-11-30 14:15 ` rguenth at gcc dot gnu.org 2020-11-30 14:47 ` abebeos at lazaridis dot com 2020-11-30 16:29 ` abebeos at lazaridis dot com 2020-11-30 23:25 ` abebeos at lazaridis dot com 2020-12-01 19:10 ` abebeos at lazaridis dot com 2020-12-02 13:03 ` abebeos at lazaridis dot com 2020-12-02 13:22 ` redi at gcc dot gnu.org 2020-12-02 13:24 ` glaubitz at physik dot fu-berlin.de 2020-12-02 13:56 ` abebeos at lazaridis dot com 2020-12-02 14:04 ` abebeos at lazaridis dot com 2020-12-03 0:37 ` abebeos at lazaridis dot com 2020-12-04 1:19 ` abebeos at lazaridis dot com 2020-12-04 19:31 ` abebeos at lazaridis dot com 2020-12-07 0:39 ` abebeos at lazaridis dot com 2020-12-07 13:02 ` abebeos at lazaridis dot com 2020-12-07 13:10 ` glaubitz at physik dot fu-berlin.de 2020-12-07 13:34 ` abebeos at lazaridis dot com 2020-12-09 13:42 ` abebeos at lazaridis dot com 2020-12-10 14:38 ` abebeos at lazaridis dot com 2020-12-12 18:24 ` abebeos at lazaridis dot com 2020-12-13 16:13 ` abebeos at lazaridis dot com 2020-12-13 22:06 ` abebeos at lazaridis dot com 2020-12-14 2:12 ` abebeos at lazaridis dot com 2020-12-16 20:46 ` abebeos at lazaridis dot com 2021-02-06 15:21 ` saaadhu at gcc dot gnu.org 2021-04-30 17:21 ` saaadhu at gcc dot gnu.org 2021-04-30 18:16 ` abebeos at lazaridis dot com 2021-04-30 18:29 ` abebeos at lazaridis dot com 2021-04-30 18:33 ` abebeos at lazaridis dot com 2021-05-01 12:40 ` shiftee at posteo dot net 2021-05-01 13:40 ` abebeos at lazaridis dot com 2021-05-01 13:42 ` glaubitz at physik dot fu-berlin.de 2021-05-01 13:52 ` abebeos at lazaridis dot com 2021-05-02 20:47 ` abebeos at lazaridis dot com 2021-05-07 23:27 ` abebeos at lazaridis dot com 2021-05-09 21:55 ` abebeos at lazaridis dot com 2021-05-12 18:34 ` abebeos at lazaridis dot com 2021-05-13 21:19 ` abebeos at lazaridis dot com 2023-06-10 19:59 ` cvs-commit at gcc dot gnu.org 2023-06-10 20:25 ` cvs-commit at gcc dot gnu.org 2023-06-10 20:46 ` cvs-commit at gcc dot gnu.org 2024-03-03 12:10 ` cvs-commit 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-92729-4-1F1Uf9vuQy@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).