Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/Semi-obvious/5.3?] Fix compilation error in hppa-tdep.c
Date: Thu, 31 Oct 2002 07:13:00 -0000	[thread overview]
Message-ID: <15807.62986.297947.502319@localhost.redhat.com> (raw)
In-Reply-To: <20021030082803.GA903@gnat.com>

Joel Brobecker writes:
 > > 2002-10-30  Joel Brobecker  <brobecker@gnat.com>
 > > 
 > >         * hppa-tdep.c (find_function_in_inferior): Fix the declaration
 > >         that caused a compilation error on HP/UX.
 > >         (low_text_segment_addres): Fix a compilation warning.
 > 
 > Actually, I am replying to myself: the fix to find_function_in_inferior
 > works, but is pretty stupid. Better to remove the extern altogether,
 > since we get the definition directly from value.h (which caused the
 > compilation error in the first place). 
 > 

Yes, externs in .c files are flagged by the ARI, and should be removed
whenever one gets a chance. Are the Makefile dependencies on value.h in place?
(I always ask, I didn't check).

Seems ok to me.

Thanks for taking upon yourself the hppa cleanup task. It is really great news!

Elena


 > Sorry about that, I should not be working that late I suppose.
 > 
 > Here is a new patch, with a new ChangeLog:
 > 
 > 2002-10-30  Joel Brobecker  <brobecker@gnat.com>
 > 
 >         * hppa-tdep.c (find_function_in_inferior): Remove this extern,
 >         as this is already provided by value.h, and was actually causing
 >         a compilation error due to a conflict in parameter type declaration
 >         due to a missing const keyword.
 >         (low_text_segment_addres): Fix a compilation warning.
 > 
 > It looks like the 5.3 branch has the same problem, so I'll fix it too
 > when I get approval for this patch.
 > 
 > Thanks,
 > -- 
 > Joel
 > Index: hppa-tdep.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/hppa-tdep.c,v
 > retrieving revision 1.28
 > diff -c -3 -p -r1.28 hppa-tdep.c
 > *** hppa-tdep.c	24 Oct 2002 21:02:53 -0000	1.28
 > --- hppa-tdep.c	30 Oct 2002 08:24:34 -0000
 > *************** extern int hp_som_som_object_present;
 > *** 149,157 ****
 >   /* In breakpoint.c */
 >   extern int exception_catchpoints_are_fragile;
 >   
 > - /* This is defined in valops.c. */
 > - extern struct value *find_function_in_inferior (char *);
 > - 
 >   /* Should call_function allocate stack space for a struct return?  */
 >   int
 >   hppa_use_struct_convention (int gcc_p, struct type *type)
 > --- 149,154 ----
 > *************** static CORE_ADDR low_text_segment_addres
 > *** 300,306 ****
 >   static void
 >   record_text_segment_lowaddr (bfd *abfd, asection *section, void *ignored)
 >   {
 > !   if ((section->flags & (SEC_ALLOC | SEC_LOAD | SEC_READONLY)
 >          == (SEC_ALLOC | SEC_LOAD | SEC_READONLY))
 >         && section->vma < low_text_segment_address)
 >       low_text_segment_address = section->vma;
 > --- 297,303 ----
 >   static void
 >   record_text_segment_lowaddr (bfd *abfd, asection *section, void *ignored)
 >   {
 > !   if (((section->flags & (SEC_ALLOC | SEC_LOAD | SEC_READONLY))
 >          == (SEC_ALLOC | SEC_LOAD | SEC_READONLY))
 >         && section->vma < low_text_segment_address)
 >       low_text_segment_address = section->vma;


  parent reply	other threads:[~2002-10-31 15:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  0:06 Joel Brobecker
2002-10-30  0:26 ` Joel Brobecker
2002-10-30  6:10   ` Daniel Jacobowitz
2002-10-30 13:09     ` Joel Brobecker
2002-10-31  7:13   ` Elena Zannoni [this message]
2002-10-31 15:46     ` Joel Brobecker
2002-10-30  6:42 ` Daniel Jacobowitz
2002-10-31  9:32   ` Andrew Cagney
2002-10-31  9:35     ` Daniel Jacobowitz
2002-10-31 13:10       ` Daniel Jacobowitz
2002-10-31 13:18         ` Andrew Cagney
2002-11-05 13:36           ` Daniel Jacobowitz

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=15807.62986.297947.502319@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.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