From: Janus Weil <janus@gcc.gnu.org>
To: Dominique Dhumieres <dominiq@lps.ens.fr>
Cc: fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
tkoenig <tkoenig@netcologne.de>
Subject: Re: [Patch, Fortran, OOP] PR 46313: OOP-ABI issue, ALLOCATE issue, CLASS renaming issue
Date: Sat, 06 Nov 2010 23:56:00 -0000 [thread overview]
Message-ID: <AANLkTingHZS-rPzupUTTdCA_iQto9NavuQ5RGAPPd57i@mail.gmail.com> (raw)
In-Reply-To: <20101106233415.7DA533BE18@mailhost.lps.ens.fr>
>> If we are going to change the naming of the OOP stuff anyway, what about
>> the possible name collisions with -fdollar-ok ?
>
> With the patch for PR 46313, the test compiled with -fdollar-ok is
> compiled without problem on x86_64-apple-darwin10.
Yes, that is expected, because the patch changes the name of the vtab
to "vtab$main$dt", so one needs to change the name of the subroutine
in the test case in the same way in order to see the failure:
program main
type :: dt
! ...
end type dt
class(dt), pointer :: cp
contains
subroutine vtab$main$dt
end subroutine vtab$main$dt
end program main
Btw, I just tried the version with '@' instead of '$'. Unfortunately
the assembler doesn't seem to like that. I get tons of errors like:
/tmp/ccToz7yL.s:3: Error: junk at end of line, first unrecognized
character is `@'
/tmp/ccToz7yL.s:4: Error: invalid character '@' in mnemonic
Are there any other special characters we can exploit? What about the
pound sign or the ampersand? Any problems to expect with these? Or
should we rather stay with the dollar and ignore the problems with
-fdollar-ok?
Cheers,
Janus
next prev parent reply other threads:[~2010-11-06 23:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 23:34 Dominique Dhumieres
2010-11-06 23:56 ` Janus Weil [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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=AANLkTingHZS-rPzupUTTdCA_iQto9NavuQ5RGAPPd57i@mail.gmail.com \
--to=janus@gcc.gnu.org \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tkoenig@netcologne.de \
/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).