public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paulthomas2 at wanadoo dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/17298] gfortran ICE: Not Implemented: Scalarization of non-elemental intrinsic: __transfer1 Date: Sat, 06 May 2006 08:02:00 -0000 [thread overview] Message-ID: <20060506080222.18620.qmail@sourceware.org> (raw) In-Reply-To: <bug-17298-6318@http.gcc.gnu.org/bugzilla/> ------- Comment #24 from paulthomas2 at wanadoo dot fr 2006-05-06 08:02 ------- Subject: Re: gfortran ICE: Not Implemented: Scalarization of non-elemental intrinsic: __transfer1 >I'm unfamiliar with Bugzilla, so if I annoy anyone, apologies. > > You made a serious comment... you won't upset anyone! > This routine is a puzzle, or else I have completely misunderstood it. The >TRANSFER is obviously spurious, as it merely allows the sort of renaming that >used to be possible with the deprecated EQUIVALENCE statement, were it to be >allowed for parameters. > > This is the nub of it; like equivalence, which is still supported in gfortran, transfer effects a bitwise mapping from source to destination. > But, why not > dcabs1 = abs(real(z)) + abs(aimag(z)) > relying on proper precision selection (or, supply d prefixes). > > ... whereas real and aimag do kind conversion, if it is necessary. > Of course, in general the TRANSFER function should work. > Best wishes, RNMcLean somewhere by yahoo.com > > In my opinion, real and aimag are better because they are likely to be more efficient; transfer is looking (as I well know!) to do the general case and needs to calculate source/destination sizes, whether or not they are packed and so on. Best regards Paul Thomas -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17298
next prev parent reply other threads:[~2006-05-06 8:02 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-17298-6318@http.gcc.gnu.org/bugzilla/> 2005-12-22 3:32 ` pinskia at gcc dot gnu dot org 2006-03-15 16:49 ` pault at gcc dot gnu dot org 2006-03-19 21:01 ` patchapp at dberlin dot org 2006-03-22 5:13 ` pault at gcc dot gnu dot org 2006-03-22 20:00 ` pault at gcc dot gnu dot org 2006-03-22 20:02 ` pault at gcc dot gnu dot org 2006-04-01 17:10 ` ebotcazou at gcc dot gnu dot org 2006-04-01 17:24 ` kargl at gcc dot gnu dot org 2006-04-01 20:05 ` ebotcazou at gcc dot gnu dot org 2006-04-01 20:48 ` kargl at gcc dot gnu dot org 2006-04-02 6:13 ` pinskia at gcc dot gnu dot org 2006-04-02 6:21 ` ebotcazou at gcc dot gnu dot org 2006-04-02 6:27 ` pinskia at gcc dot gnu dot org 2006-04-02 6:36 ` ebotcazou at gcc dot gnu dot org 2006-04-02 6:38 ` ebotcazou at gcc dot gnu dot org 2006-04-03 21:01 ` pinskia at gcc dot gnu dot org 2006-05-03 1:51 ` RNMcLean at yahoo dot com 2006-05-06 8:02 ` paulthomas2 at wanadoo dot fr [this message] 2004-09-02 20:20 [Bug fortran/17298] New: " anlauf at hep dot tu-darmstadt dot de 2004-09-08 19:00 ` [Bug fortran/17298] " toon at moene dot indiv dot nluug dot nl 2004-11-10 9:13 ` c dot lemmen at fz-juelich dot de 2005-02-22 22:38 ` pinskia at gcc dot gnu dot org 2005-03-15 16:28 ` pinskia at gcc dot gnu dot org 2005-06-09 9:35 ` c dot lemmen at fz-juelich dot de 2005-06-09 9:42 ` tobi 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=20060506080222.18620.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: linkBe 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).