public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Koning <paulkoning@comcast.net>
Cc: Richard Biener <richard.guenther@gmail.com>,
	Gerald Pfeifer <gerald@pfeifer.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] wwwdocs: Note that old reload is deprecated
Date: Wed, 11 Jan 2023 13:28:50 -0600	[thread overview]
Message-ID: <20230111192850.GX25951@gate.crashing.org> (raw)
In-Reply-To: <F29F260B-90D6-4330-9562-B4571CE17601@comcast.net>

On Wed, Jan 11, 2023 at 01:42:22PM -0500, Paul Koning wrote:
> Or, as in my case, because building with LRA as the default triggers an ICE that I don't understand.  I posted a note to the GCC list about what I saw, but have received no reaction.

<https://gcc.gnu.org/pipermail/gcc/2023-January/240497.html>?

I would say your predicates are way too lenient here (general_operand),
but this needs more info.  A testcase to reproduce the problem, to
start with :-)


Segher

  reply	other threads:[~2023-01-11 19:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 19:27 Segher Boessenkool
2023-01-05 19:54 ` Paul Koning
2023-01-05 20:23   ` Segher Boessenkool
2023-01-11 14:21 ` Gerald Pfeifer
2023-01-11 14:34   ` Richard Biener
2023-01-11 15:15     ` Segher Boessenkool
2023-01-11 16:27       ` Richard Biener
2023-01-11 18:32         ` Segher Boessenkool
2023-01-11 18:39           ` Richard Biener
2023-01-11 19:07             ` Segher Boessenkool
2023-01-12  7:44               ` Richard Biener
2023-01-12  7:48                 ` Richard Biener
2023-01-11 18:42           ` Paul Koning
2023-01-11 19:28             ` Segher Boessenkool [this message]
2023-01-11 22:07               ` Paul Koning
2023-01-12  9:50                 ` Segher Boessenkool
2023-01-12 14:17                   ` Paul Koning
2023-01-12 14:40                     ` Segher Boessenkool
2023-01-12 15:07                       ` Paul Koning

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=20230111192850.GX25951@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=paulkoning@comcast.net \
    --cc=richard.guenther@gmail.com \
    /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).