public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Tobias dot Schlueter at physik dot uni-muenchen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20178] COMPLEX function returns incompatible with g77
Date: Sun, 22 May 2005 18:10:00 -0000	[thread overview]
Message-ID: <20050522181027.12251.qmail@sourceware.org> (raw)
In-Reply-To: <20050223185848.20178.stevenj@fftw.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]


------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de  2005-05-22 18:10 -------
Subject: Re:  COMPLEX function returns incompatible with
 g77

Tobias Schlüter wrote:
>>>------- Additional Comments From tobi at gcc dot gnu dot org  2005-05-10 22:23 -------
>>>Fixed on the mainline.  I will commit this to the branch after the obligatory
>>>testing and the necessary changes (unfortunately -fsecond-underscore became the
>>>default on the branch).
>>
>>
>>[ Sorry for the late reply ]
>>
>>I wonder if that really means we have to stick to -fsecond-underscore on 
>>the 4.0 branch.  Only 4.0.0 is out, and it is very probable that 
>>*nobody* uses it for any serious work in Fortran anyway.
>>
>>I feel we can safely change the default, even on the branch.
> 
> 
> I'm also inclined to doing this, 4.0.1 will probably be vastly more usable
> than 4.0, but I'd still like to get feedback from the list.  It's really a
> minor incompatibility.  Especially since a lot of people seem to use
> '-fno-second-underscore'.

I'll commit this during the week, unless somebody objects.  Toon's approval
together with no objections so far is enough for me, but I wanted to give
everybody a last chance to object.

- Tobi


-- 


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


  parent reply	other threads:[~2005-05-22 18:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 23:29 [Bug fortran/20178] New: " gcc-bugzilla at gcc dot gnu dot org
2005-02-23 23:32 ` [Bug fortran/20178] " pinskia at gcc dot gnu dot org
2005-02-24  2:42 ` tobi at gcc dot gnu dot org
2005-02-24  2:43 ` tobi at gcc dot gnu dot org
2005-02-24  4:39 ` pinskia at gcc dot gnu dot org
2005-02-24  7:31 ` tobi at gcc dot gnu dot org
2005-02-24  9:27 ` pinskia at gcc dot gnu dot org
2005-02-24  9:27 ` stevenj at fftw dot org
2005-02-24  9:27 ` pinskia at gcc dot gnu dot org
2005-02-24 10:30 ` tobi at gcc dot gnu dot org
2005-02-24 10:35 ` stevenj at fftw dot org
2005-02-24 10:58 ` stevenj at fftw dot org
2005-02-28  2:50 ` tobi at gcc dot gnu dot org
2005-03-03 20:51 ` tobi at gcc dot gnu dot org
2005-03-03 21:36 ` tobi at gcc dot gnu dot org
2005-03-03 21:49 ` stevenj at fftw dot org
2005-03-03 22:06 ` tobi at gcc dot gnu dot org
2005-03-04  4:44 ` stevenj at fftw dot org
2005-03-04  4:46 ` stevenj at fftw dot org
2005-03-04 11:27 ` tobi at gcc dot gnu dot org
2005-03-04 11:40 ` tobi at gcc dot gnu dot org
2005-03-05 15:33 ` tobi at gcc dot gnu dot org
2005-05-10 22:07 ` cvs-commit at gcc dot gnu dot org
2005-05-10 22:23 ` tobi at gcc dot gnu dot org
     [not found] ` <19490500.1116054120820.JavaMail.root@dtm1eusosrv72.dtm.ops.eu.uu.net>
2005-05-15 11:32   ` Toon Moene
2005-05-15 11:34 ` toon at moene dot indiv dot nluug dot nl
2005-05-18 11:23 ` Tobias dot Schlueter at physik dot uni-muenchen dot de
2005-05-22 18:10 ` Tobias dot Schlueter at physik dot uni-muenchen dot de [this message]
2005-07-20 23:13 ` pinskia at gcc dot gnu dot org
2005-07-22 13:42 ` tobi at gcc dot gnu dot org
     [not found] <bug-20178-9955@http.gcc.gnu.org/bugzilla/>
2006-01-31 18:01 ` pinskia 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=20050522181027.12251.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).