public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/113823] ice in gfc_get_element_type, at fortran/trans-types.cc:1286
Date: Thu, 08 Feb 2024 21:26:32 +0000 [thread overview]
Message-ID: <bug-113823-4-rP71ltLYnb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113823-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113823
--- Comment #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Feb 08, 2024 at 08:43:08PM +0000, dcb314 at hotmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113823
>
> --- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
> (In reply to Steve Kargl from comment #5)
> > That's not what I meant. There is no bug1006.f90 in
> > the llvm-project repo. What is the actual URL to the
> > actual testcase? It should look something like
> >
> > https://github.com/llvm/llvm-project/tree/main/flang/test/bug1006.f90
>
> bug1006.f90 is my local file name for it.
>
> It is just a copy of the original file
> Lower/HLFIR/array-ctor-derived.f90 in the flang test suite.
>
> That has an URL of
> https://github.com/llvm/llvm-project/tree/main/flang/test/Lower/HLFIR/array-ctor-derived.f90
>
Thanks. This may allow a gfortran contributor to see how
other developers handled the code. Although not with this
bug report, some contain an analysis of what the Fortran
standard requires with a particular piece of code.
prev parent reply other threads:[~2024-02-08 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 8:13 [Bug fortran/113823] New: " dcb314 at hotmail dot com
2024-02-08 15:29 ` [Bug fortran/113823] " kargl at gcc dot gnu.org
2024-02-08 15:48 ` dcb314 at hotmail dot com
2024-02-08 17:56 ` kargl at gcc dot gnu.org
2024-02-08 19:38 ` dcb314 at hotmail dot com
2024-02-08 20:02 ` sgk at troutmask dot apl.washington.edu
2024-02-08 20:43 ` dcb314 at hotmail dot com
2024-02-08 21:26 ` sgk at troutmask dot apl.washington.edu [this message]
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-113823-4-rP71ltLYnb@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).