public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Valera.Veryazov@teokem.lu.se
To: gcc-gnats@gcc.gnu.org
Subject: fortran/5837: bug in loop unrolling
Date: Tue, 05 Mar 2002 05:46:00 -0000	[thread overview]
Message-ID: <20020305133903.19118.qmail@sources.redhat.com> (raw)


>Number:         5837
>Category:       fortran
>Synopsis:       bug in loop unrolling
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 05 05:46:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Valera.Veryazov@teokem.lu.se
>Release:        3.0.4
>Organization:
>Environment:
Linux Mandrake 8.1. GCC/G77 compiled from the source code.
>Description:
The code (see attachment) produces a Segnematation fault,
if flags " -O  -funroll-loops" are used.

Change of parameter to 12, 16 gives a correct result.
Also, a change of declaration Character *64 to, say,
Character*45 produces a funny number instead 0.

Removing -unroll-loops flag or using unrolling by hands
also 'fix' the problem.

>How-To-Repeat:
just compile the code with -O  -funroll-loops flags.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="main.f"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="main.f"

YyAgICAgZzc3ICAtTyAgLWZ1bnJvbGwtbG9vcHMgICBtYWluLmYKICAgICAgcHJvZ3JhbSBtYWlu
CiAgICAgIFBhcmFtZXRlciAobiA9IDExKSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgIAogICAgICBDb21tb24gL1RULyBNTQogICAgICBDaGFyYWN0ZXIqNjQgRmxkKG4pLFN0YXQo
bikgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAKICAgICAgQ29tbW9uIC9USU1DLyBGbGQsU3RhdCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgCioKICAgICAgTU09MAogICAgICBkbyBpPTEsbgogICAgICAgIEZs
ZChpKT0nICcKICAgICAgICBTdGF0KGkpPScgJwogICAgICBlbmQgZG8KICAgICAgd3JpdGUoKiwq
KSBNTQogICAgICBlbmQK


             reply	other threads:[~2002-03-05 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-05  5:46 Valera.Veryazov [this message]
2002-04-13  7:23 toon

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=20020305133903.19118.qmail@sources.redhat.com \
    --to=valera.veryazov@teokem.lu.se \
    --cc=gcc-gnats@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).