public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34107] seg fault when writing into character variable when code compiled with -maling-double
Date: Thu, 15 Nov 2007 10:54:00 -0000	[thread overview]
Message-ID: <20071115105400.14722.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34107-15360@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from pault at gcc dot gnu dot org  2007-11-15 10:54 -------
Jens,

I cannot reproduce this bug, even with the same flags that you are using, under
Cygwin_NT and last night's build.  I will check on a Linux system tonight.

I have downrated the severity because "critical" refers to bugs that prevent
the gcc build.  I assure you that the gfortran maintainers will take the report
just as seriously.

Thanks for the report

Paul


-- 

pault at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pault at gcc dot gnu dot org
           Severity|critical                    |normal


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34107


  reply	other threads:[~2007-11-15 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 10:24 [Bug fortran/34107] New: " j dot m dot h dot thomas at dl dot ac dot uk
2007-11-15 10:54 ` pault at gcc dot gnu dot org [this message]
2007-11-15 11:26 ` [Bug fortran/34107] " rguenth at gcc dot gnu dot org
2007-11-15 11:58 ` pault at gcc dot gnu dot org
2007-11-15 14:57 ` jvdelisle at gcc dot gnu dot 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=20071115105400.14722.qmail@sourceware.org \
    --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).