From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: wilson@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: egcs-980315, WARNING fixes part 2 (minor addition)
Date: Thu, 19 Mar 1998 21:47:00 -0000 [thread overview]
Message-ID: <199803191537.KAA22729@caip.rutgers.edu> (raw)
> From: Jim Wilson <wilson@cygnus.com>
> Subject: Re: egcs-980315, WARNING fixes part 2 (minor addition)
>
> This is OK to install.
> Jim
Done, (slightly modified to follow Robert's suggestion below,
hope that's ok.)
--Kaveh
> From: Robert Lipe <robertl@dgii.com>
> To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
> Subject: Re: egcs-980315, WARNING fixes part 2 (minor addition)
> References: < 199803171537.KAA10985@caip.rutgers.edu >
> Mime-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> X-Mailer: Mutt 0.89
> In-Reply-To: < 199803171537.KAA10985@caip.rutgers.edu >; from Kaveh R. Ghazi on Tue, Mar 17, 1998 at 10:37:06AM -0500
> Status: RO
>
> > diff -rup orig/egcs-980315/gcc/flow.c egcs-980315/gcc/flow.c
> > --- orig/egcs-980315/gcc/flow.c Mon Mar 16 22:21:59 1998
> > +++ egcs-980315/gcc/flow.c Mon Mar 16 22:13:53 1998
> > @@ -961,7 +961,9 @@ life_analysis (f, nregs, file)
> > int nregs;
> > FILE *file;
> > {
> > +#ifdef ELIMINABLE_REGS
> > register size_t i;
> > +#endif
> >
> > #ifdef ELIMINABLE_REGS
> > static struct {int from, to; } eliminables[] = ELIMINABLE_REGS;
>
> Can these just be smooshed together rather than having two consecutive
> identical #ifdefs?
>
> No justification necessary regardless of what you decide...
> RJL
--
Kaveh R. Ghazi Project Manager / Custom Development
ghazi@caip.rutgers.edu Icon CMT Corp.
next reply other threads:[~1998-03-19 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-19 21:47 Kaveh R. Ghazi [this message]
1998-03-19 15:36 ` Jim Wilson
-- strict thread matches above, loose matches on Subject: below --
1998-03-17 8:42 Kaveh R. Ghazi
1998-03-18 16:14 ` Jim Wilson
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=199803191537.KAA22729@caip.rutgers.edu \
--to=ghazi@caip.rutgers.edu \
--cc=egcs@cygnus.com \
--cc=wilson@cygnus.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).