From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
To: gcc-patches@gcc.gnu.org, fortran@gcc.gnu.org
Cc: Nathan Froyd <froydnj@codesourcery.com>
Subject: Re: [PATCH] get rid of some TYPE_ARG_TYPES usage by introducing nth_arg_type
Date: Tue, 24 May 2011 11:16:00 -0000 [thread overview]
Message-ID: <20110524082643.GA26691@physik.fu-berlin.de> (raw)
On Mon 23 May 2011, Nathan Froyd wrote:
> Various places in the compiler grab TYPE_ARG_TYPES and grovel through it
> when what they're really trying to do is index into the list of argument
> types. The patch below introduces nth_arg_type for such situatiosn and
> changes a hodgepodge of places to use it. You could, of course, use
> function_args_iterator, but I think this approach is somewhat clearer.
>
> Tested on x86_64-unknown-linux-gnu. OK to commit?
> gcc/fortran/
> * trans-decl.c (create_main_function): Call nth_arg_type.
The Fortran part is OK.
Thanks for the cleanup!
Tobias
next reply other threads:[~2011-05-24 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 11:16 Tobias Burnus [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-23 14:55 Nathan Froyd
2011-05-23 14:57 ` Richard Guenther
2011-05-23 14:57 ` Nathan Froyd
2011-05-23 15:02 ` Jason Merrill
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=20110524082643.GA26691@physik.fu-berlin.de \
--to=tobias.burnus@physik.fu-berlin.de \
--cc=fortran@gcc.gnu.org \
--cc=froydnj@codesourcery.com \
--cc=gcc-patches@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).