This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [patch/rfc] Eliminate char buf[MAX_REGISTER_RAW_SIZE]
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: Joel Brobecker <brobecker at gnat dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Sat, 01 Feb 2003 01:40:15 -0500
- Subject: Re: [patch/rfc] Eliminate char buf[MAX_REGISTER_RAW_SIZE]
- References: <3E3AFFA5.9080902@redhat.com> <20030201061310.GB22468@gnat.com>
I have a simple (stupid?) question: Generaly speaking, is there a
prefered form between the following two?
max_register_raw_size (current_gdbarch)
or
MAX_REGISTER_RAW_SIZE
These two forms are exactly equivalent, but in most occurences I've seen
in the code, we used the macro... But maybe you used the non-macro form
to show that we do an alloca because the size of the buffer is not known
at compile-time?
Old == MAX_REGISTER_RAW_SIZE, MAX_REGISTER_VIRTUAL_SIZE.
New == max_register_size (current_gdbarch)
The old macro's will eventually go away.
Andrew