public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/34887] reverse tabbing before slash descriptor (regression vs. g77)
Date: Thu, 24 Jan 2008 22:37:00 -0000	[thread overview]
Message-ID: <20080124220908.25197.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34887-10743@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from tkoenig at gcc dot gnu dot org  2008-01-24 22:09 -------

> This causes a regression in x_slash_1.f .  I'll dig around
> some more.

There's something wrong here (as evidenced in the PR :-)
In next_record_w, we should be following the path starting with
if (done) every time, to get this right.

I'm not 100% sure what

                      length = (int) (max_pos - m);
                      p = salloc_w (dtp->u.p.current_unit->s, &length);  

does when we never write to the memory pointed to by p. Maybe
this is used as an idiom to mark the memory, which may have
been written to earlier, as "dirty".  It's horrible in any case :-)


-- 


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


  parent reply	other threads:[~2008-01-24 22:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-20 19:07 [Bug libfortran/34887] New: NIST FM903.f anomaly jvdelisle at gcc dot gnu dot org
2008-01-20 21:21 ` [Bug libfortran/34887] reverse tabbing before slash descriptor (regression vs. g77) tkoenig at gcc dot gnu dot org
2008-01-20 21:56 ` tkoenig at gcc dot gnu dot org
2008-01-20 22:20 ` tkoenig at gcc dot gnu dot org
2008-01-20 22:31 ` tkoenig at gcc dot gnu dot org
2008-01-24 22:37 ` tkoenig at gcc dot gnu dot org [this message]
2008-01-25  2:18 ` jvdelisle at gcc dot gnu dot org
2008-01-26  9:51 ` tkoenig at gcc dot gnu dot org
2008-01-26 16:27 ` tkoenig at gcc dot gnu dot org
2008-01-26 16:29 ` tkoenig 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=20080124220908.25197.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).