public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Marek Polacek <polacek@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
	 java-patches@gcc.gnu.org,  GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Java PATCH] Generate declarations in jvgenmain.c
Date: Tue, 07 Oct 2014 16:41:00 -0000	[thread overview]
Message-ID: <87bnpnrfz2.fsf@tromey.com> (raw)
In-Reply-To: <20141007161518.GI3503@redhat.com> (Marek Polacek's message of	"Tue, 7 Oct 2014 18:15:19 +0200")

Marek> I saw declarations of JvRunMain{,Name} with no parameters and with
Marek> some parameters.

Oh yeah, duh.

Marek>  So I decided to make it prototype-less function
Marek> declaration for now.  I think we don't have to worry about
Marek> -Wstrict-prototypes for now.

Thanks for looking.

Tom

      reply	other threads:[~2014-10-07 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07  8:31 Marek Polacek
2014-10-07 12:21 ` Andrew Haley
2014-10-07 16:03 ` Tom Tromey
2014-10-07 16:15   ` Marek Polacek
2014-10-07 16:41     ` Tom Tromey [this message]

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=87bnpnrfz2.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=polacek@redhat.com \
    /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).