public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Zdenek Dvorak <rakdver@atrey.karlin.mff.cuni.cz>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Diego Novillo <dnovillo@redhat.com>,
Graham Stott <graham.stott@btinternet.com>,
gcc-bugs@gcc.gnu.org, Jan Hubicka <jh@suse.cz>
Subject: Re: java/io/natFile.cc:106: internal compiler error: verify_ssa failed.
Date: Sat, 11 Sep 2004 11:58:00 -0000 [thread overview]
Message-ID: <20040911115849.GA8345@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.60.0409110752490.5290@dberlin.org>
Hello,
> >>While you are around there, can you rename it to tree-loop-ivopts?
> >>
> >>(I have no idea why zdenek keeps naming switches in ways that are
> >>completely different than how we've been naming them :P).
> >
> >since I do not like the convention.
>
> This is not a good reason.
>
> If you want to convert *all* the switches, do so.
> If not, the new switches should be consistent with the old ones.
>
> Understand that I could care less whether it's -fivopts or -fivcanon. I
> care that it's not consistent with the existing options.
>
> Being consistent in our interface to the user is important.
> Simply because you don't like the existing convention doesn't mean you
> should just start using your own.
should not this remark apply to the first person creating a
-ftree-anything switch? I just (unlike this first person) stick with
the older convention that there is no such convention and everyone just
names the switches the way he likes :-).
Zdenek
next prev parent reply other threads:[~2004-09-11 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 14:31 Graham Stott
2004-09-05 14:50 ` Diego Novillo
2004-09-05 15:11 ` Graham Stott
2004-09-05 17:18 ` Graham Stott
2004-09-05 17:54 ` Diego Novillo
2004-09-05 18:22 ` Daniel Berlin
2004-09-11 11:45 ` Zdenek Dvorak
2004-09-11 11:54 ` Daniel Berlin
2004-09-11 11:58 ` Zdenek Dvorak [this message]
2004-09-11 12:02 ` Daniel Berlin
2004-09-06 8:47 ` Jan Hubicka
2004-09-06 12:21 ` Jan Hubicka
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=20040911115849.GA8345@atrey.karlin.mff.cuni.cz \
--to=rakdver@atrey.karlin.mff.cuni.cz \
--cc=dberlin@dberlin.org \
--cc=dnovillo@redhat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=graham.stott@btinternet.com \
--cc=jh@suse.cz \
/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).