public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/84868] [11/12/13/14/15 Regression] ICE in gfc_conv_descriptor_offset, at fortran/trans-array.c:208
Date: Sat, 13 Jul 2024 07:20:21 +0000	[thread overview]
Message-ID: <bug-84868-4-92LRaPgAbH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84868-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Paul Thomas from comment #16)
> Created attachment 58641 [details]
> Fix for this PR
> 
> The only way that I have found to fix this is to simplify the len_trim
> expression. In doing so, another parameter has to be created for which I
> have taken a leaf out of the unique_name mechanism. Unfortunately, two such
> parameters are created (parsing specification expression and then
> resolution), the first one of which is unused. I don't see any easy way to
> eliminate it.
> 
> I came across another bug in testing variants, which is also fixed. Regtests
> OK.
> 
> I'll think further about doubling up on the parameter before submitting.
> 
> Paul

I have figured out how to eliminate the duplicate parameter. I will be
submitting to the list very soon :-)

Cheers

Paul

  parent reply	other threads:[~2024-07-13  7:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-84868-4@http.gcc.gnu.org/bugzilla/>
2021-05-14  9:50 ` [Bug fortran/84868] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:10 ` rguenth at gcc dot gnu.org
2022-05-27  9:38 ` [Bug fortran/84868] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:34 ` jakub at gcc dot gnu.org
2023-07-07 10:33 ` [Bug fortran/84868] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-04-26  9:51 ` pault at gcc dot gnu.org
2024-07-12  9:43 ` [Bug fortran/84868] [11/12/13/14/15 " pault at gcc dot gnu.org
2024-07-12 11:47 ` pault at gcc dot gnu.org
2024-07-13  7:20 ` pault at gcc dot gnu.org [this message]
2024-07-16 14:56 ` cvs-commit at gcc dot gnu.org
2024-07-19 13:02 ` [Bug fortran/84868] [12/13/14 " rguenth 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-84868-4-92LRaPgAbH@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).