From: Andrew Cagney <ac131313@cygnus.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gdb-patches@sources.redhat.com, insight@sources.redhat.cmo
Subject: Re: multi-arched alpha won't build with OSF1 4.0d's cc
Date: Sun, 05 May 2002 11:14:00 -0000 [thread overview]
Message-ID: <3CD57683.9000506@cygnus.com> (raw)
In-Reply-To: <or4rhmr37o.fsf@livre.redhat.lsd.ic.unicamp.br>
> OSF1 4.0d's cc complains when a non-constant value is used as the
> array size of a formal parameter. The first patch below fixes the
> problem without removing the documentation value of the array size at
> that point. I wonder if just commenting out the (variable) array size
> would be a better choice.
>
> It also rightfully refuses to compile functions containing automatic
> arrays of non-constant sizes. The second patch below fixes this
> problem.
>
> With these two patches, GDB mainline builds on this platform again,
> using this picky/dumb compiler.
>
> Ok to install?
>
Yes (if you haven't already).
I'll add '\[MAX_REGISTER_{RAW,VIRTUAL}_SIZE\]' to the ARI.
Andrew
prev parent reply other threads:[~2002-05-05 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 9:04 Alexandre Oliva
2002-05-05 10:17 ` Jason R Thorpe
2002-05-05 11:14 ` Andrew Cagney [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=3CD57683.9000506@cygnus.com \
--to=ac131313@cygnus.com \
--cc=aoliva@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=insight@sources.redhat.cmo \
/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