public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asl at math dot spbu dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33097] Function decl trees without proper argument list
Date: Wed, 17 Oct 2007 16:45:00 -0000	[thread overview]
Message-ID: <20071017164547.17000.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33097-14919@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from asl at math dot spbu dot ru  2007-10-17 16:45 -------
(In reply to comment #3)
> Two decls are generated for function x, the first one (inside MAIN__) doesn't
> have a proper argument list while the second one is OK. When I try to make
> gfortran emit only one decl per externally-visible function, it's currently
> choking on this.
After some thinking on this example, it seems, I found some solution. My
previous approach cannot be completed because of the presence of optional
arguments. And even having some valid call, we cannot construct valid decl from
this (or we will need some additional logic, which will "complete" such decls).

The idea itself is pretty simple: why don't turn external functions/intrinsics
into varargs function (in C/C++ sense). In this case trees won't became bogus
anymore, however, having call to varargs function can (in theory) disable some
optimization performed on it. Attached patch works fine for me. Any comments?


-- 


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


  parent reply	other threads:[~2007-10-17 16:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-17 12:39 [Bug fortran/33097] New: Invalid decl trees are created for external intrinsics asl at math dot spbu dot ru
2007-08-17 12:42 ` [Bug fortran/33097] " asl at math dot spbu dot ru
2007-08-17 12:49 ` asl at math dot spbu dot ru
2007-08-20 14:48 ` [Bug fortran/33097] Function decl trees without proper argument list fxcoudert at gcc dot gnu dot org
2007-08-20 16:47 ` asl at math dot spbu dot ru
2007-08-20 16:48 ` asl at math dot spbu dot ru
2007-08-20 16:51 ` fxcoudert at gcc dot gnu dot org
2007-08-20 17:00 ` asl at math dot spbu dot ru
2007-10-17 10:17 ` asl at math dot spbu dot ru
2007-10-17 16:45 ` asl at math dot spbu dot ru [this message]
2007-10-17 16:46 ` asl at math dot spbu dot ru
2007-10-17 17:00 ` asl at math dot spbu dot ru
2007-10-17 17:14 ` fxcoudert at gcc dot gnu dot org
2007-10-17 17:28 ` asl at math dot spbu dot ru
2009-01-03 21:31 ` dfranke at gcc dot gnu dot org
2010-05-01 20:20 ` dfranke at gcc dot gnu dot org
2010-07-15 23:06 ` steven at gcc dot gnu dot org
2010-07-16  7:17 ` burnus at gcc dot gnu dot org
     [not found] <bug-33097-4@http.gcc.gnu.org/bugzilla/>
2010-10-06 19:37 ` howarth at nitro dot med.uc.edu
2011-03-25 19:52 ` burnus at gcc dot gnu.org
2020-06-14 15:24 ` tkoenig at gcc dot gnu.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=20071017164547.17000.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).