public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arjen.markus895 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/114626] New: Very long time for compilation the attached program, depends on value of a parameter
Date: Sun, 07 Apr 2024 08:46:47 +0000	[thread overview]
Message-ID: <bug-114626-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114626
           Summary: Very long time for compilation the attached program,
                    depends on value of a parameter
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: arjen.markus895 at gmail dot com
  Target Milestone: ---

Created attachment 57894
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57894&action=edit
Source of the program causing the very long compile time

The attached program causes the gfortran compiler to take a very long time if
the parameter max_ij is set to 100. It may not even finish. If the parameter is
set to 13 (to at least give one result), it takes a few seconds but at least
finishes in a reasonable time.

This is with default compile options. I have not tried specific options.

(Note: it is a silly program, meant for demonstration only.)

             reply	other threads:[~2024-04-07  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07  8:46 arjen.markus895 at gmail dot com [this message]
2024-04-07 18:30 ` [Bug fortran/114626] " anlauf at gcc dot gnu.org
2024-04-08  6:22 ` arjen.markus895 at gmail dot com
2024-04-08 20:39 ` anlauf 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-114626-4@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).