public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ismail at donmez dot ws" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67063] segfault in opening a formatted file at second time with status="replace"
Date: Tue, 04 Aug 2015 17:43:00 -0000 [thread overview]
Message-ID: <bug-67063-4-xfTqu8vyPp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67063-4@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3164 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67063
İsmail Dönmez <ismail at donmez dot ws> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ismail at donmez dot ws
--- Comment #5 from İsmail Dönmez <ismail at donmez dot ws> ---
You can try with my 6.x snapshots from https://i10z.com/mingw-w64/6.x/ , I
tested your testcase and it works fine.
>From gcc-bugs-return-494111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Aug 04 18:14:00 2015
Return-Path: <gcc-bugs-return-494111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82186 invoked by alias); 4 Aug 2015 18:13:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79191 invoked by uid 48); 4 Aug 2015 18:13:56 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66311] [5/6 Regression] Problems with some integer(16) values
Date: Tue, 04 Aug 2015 18:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.1.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-66311-4-DV9TXX7WIg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66311-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66311-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-08/txt/msg00253.txt.bz2
Content-length: 798
https://gcc.gnu.org/bugzilla/show_bug.cgi?idf311
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #12 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Created attachment 36128
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id6128&actioníit
Alternative patch
Here's an alternative patch. I haven't yet tested it beyond
an expanded version of the testcase, but I think it's easier
to follow if we separate the "val != valres" and "need an extra
zero block" logic.
next prev parent reply other threads:[~2015-08-04 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 1:36 [Bug fortran/67063] New: " textdirected at gmail dot com
2015-07-30 9:14 ` [Bug fortran/67063] " dominiq at lps dot ens.fr
2015-07-31 0:24 ` textdirected at gmail dot com
2015-08-03 21:38 ` fxcoudert at gcc dot gnu.org
2015-08-04 6:59 ` textdirected at gmail dot com
2015-08-04 17:43 ` ismail at donmez dot ws [this message]
2015-08-05 3:37 ` textdirected at gmail dot com
2015-08-08 20:25 ` fxcoudert 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-67063-4-xfTqu8vyPp@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).