From: Janus Weil <janus@gcc.gnu.org>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: Tobias Burnus <burnus@net-b.de>, gfortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch, Fortran, OOP] PR 46313: OOP-ABI issue, ALLOCATE issue, CLASS renaming issue
Date: Thu, 20 Sep 2018 19:36:00 -0000 [thread overview]
Message-ID: <CAKwh3qjTOhf5mT+C5oSTj+vfvBYrm=RtrjFE=QfguJ=xdgqNUw@mail.gmail.com> (raw)
In-Reply-To: <CAC1BbcSrRv=8TWwq5ARnkwomPtEbAcG8NLSKbrr_XbeBC0p1mg@mail.gmail.com>
Am Mi., 19. Sep. 2018 um 16:50 Uhr schrieb Bernhard Reutner-Fischer
<rep.dot.nop@gmail.com>:
>
> On Mon, 17 Sep 2018 at 22:25, Janus Weil <janus@gcc.gnu.org> wrote:
>
> > The regtest was successful. I don't think the off-by-two error for the
> > vtab/vtype comparisons is a big problem in practice, since the number
> > of internal symbols with leading underscores is very limited, but of
> > course it should still be fixed ...
>
> Luckily it should make no difference indeed as "__vta" and "__vtyp"
> are only used for this one purpose.
> I don't think the DTIO op keyword fix would hit any real user either.
> Thanks for taking care of it, patch LGTM.
I have now committed this as r264448.
Cheers,
Janus
next prev parent reply other threads:[~2018-09-20 19:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 20:11 Janus Weil
2010-11-06 21:03 ` Thomas Koenig
2010-11-06 21:23 ` Janus Weil
2010-11-07 16:52 ` Tobias Burnus
2010-11-07 18:44 ` Janus Weil
2010-11-08 13:27 ` Tobias Burnus
2010-11-09 10:41 ` Janus Weil
2018-09-17 8:59 ` Bernhard Reutner-Fischer
2018-09-17 19:22 ` Janus Weil
2018-09-17 20:25 ` Janus Weil
2018-09-19 14:50 ` Bernhard Reutner-Fischer
2018-09-20 19:36 ` Janus Weil [this message]
2010-11-06 23:34 Dominique Dhumieres
2010-11-06 23:56 ` Janus Weil
2010-11-07 7:55 ` Tobias Burnus
2010-11-07 12:04 ` Janus Weil
2010-11-07 12:11 ` Tobias Schlüter
2010-11-07 13:19 ` Tobias Burnus
2010-11-07 14:21 ` Janus Weil
2010-11-07 15:34 ` Tobias Schlüter
2010-11-07 15:50 ` Janus Weil
2010-11-07 16:39 ` Tobias Schlüter
2010-11-07 16:30 ` Steve Kargl
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='CAKwh3qjTOhf5mT+C5oSTj+vfvBYrm=RtrjFE=QfguJ=xdgqNUw@mail.gmail.com' \
--to=janus@gcc.gnu.org \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@gmail.com \
/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).