public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fiesh at zefix dot tv" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105753] [avr] ICE: in add_clobbers, at config/avr/avr-dimode.md:2705
Date: Wed, 01 Feb 2023 07:48:28 +0000	[thread overview]
Message-ID: <bug-105753-4-XobkcMJD3h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105753-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105753

--- Comment #13 from fiesh at zefix dot tv ---
User99627, a few points:

* My test case does require lto to be present.  There's nothing to be gained
from your statement that the bug doesn't require lto, there are test cases for
either case.  The reason I included it is that it may exhibit different
behavior which may or may not stem from a separate bug, so it's worth checking
if both test cases are resolved by a resolution to this issue.

* While this appears to be of life or death importance to you, this may not be
the same for everyone working on gcc, as reflected by its P3 importance.

* Why do you use "dysfuctional software?"  You should avoid doing that.

* Attacking people usually does not improve their willingness to help you,
especially when you don't pay them to help you.

* While you failed to provide anything meaningful to the bug report (your code
snippet is not self-contained valid C code;  no one here will care about your
attempts to get package maintainers of software distributions to do something
stupid and restrict the versions of software they include based on your
preferences), you are still welcome to fix the bug in gcc and provide a patch
yourself.

  parent reply	other threads:[~2023-02-01  7:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 22:35 [Bug target/105753] New: " filip.hejsek at gmail dot com
2022-05-28  2:55 ` [Bug target/105753] " filip.hejsek at gmail dot com
2022-06-04 22:19 ` pinskia at gcc dot gnu.org
2022-06-12 23:41 ` filip.hejsek at gmail dot com
2022-06-12 23:48 ` pinskia at gcc dot gnu.org
2022-09-11 10:19 ` triffid.hunter at gmail dot com
2022-09-25 21:45 ` pinskia at gcc dot gnu.org
2022-10-02  8:06 ` rainer-gcc at wwad dot de
2022-12-09 14:26 ` fiesh at zefix dot tv
2022-12-09 14:31 ` fiesh at zefix dot tv
2023-01-25 18:45 ` user99627 at gmx dot com
2023-01-25 19:39 ` user99627 at gmx dot com
2023-01-31 23:26 ` user99627 at gmx dot com
2023-02-01  7:48 ` fiesh at zefix dot tv [this message]
2023-02-01 10:36 ` user99627 at gmx dot com
2023-04-20 19:55 ` gjl at gcc dot gnu.org
2023-04-20 20:40 ` [Bug rtl-optimization/105753] " gjl at gcc dot gnu.org
2023-04-21  7:47 ` gjl at gcc dot gnu.org
2023-04-21  9:00 ` gjl at gcc dot gnu.org
2023-04-23 10:58 ` gjl at gcc dot gnu.org
2023-05-20  5:53 ` cvs-commit at gcc dot gnu.org
2023-05-20  6:20 ` cvs-commit at gcc dot gnu.org
2023-05-20  6:35 ` cvs-commit at gcc dot gnu.org
2023-05-20  6:46 ` gjl 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-105753-4-XobkcMJD3h@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).