public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Olivier Hainque <hainque@ACT-Europe.FR>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/9961: [3.4:cygwin] gcc/ada/raise.c:640: warning
Date: Wed, 05 Mar 2003 10:26:00 -0000	[thread overview]
Message-ID: <20030305102602.18586.qmail@sources.redhat.com> (raw)

The following reply was made to PR ada/9961; it has been noted by GNATS.

From: Olivier Hainque <hainque@ACT-Europe.FR>
To: David.Billinghurst@riotinto.com
Cc: gcc-gnats@gcc.gnu.org, hainque@ACT-Europe.FR, bosch@gnat.com
Subject: Re: ada/9961: [3.4:cygwin] gcc/ada/raise.c:640: warning
Date: Wed, 5 Mar 2003 11:25:41 +0100

 Hello David,
 
 David.Billinghurst@riotinto.com wrote:
 > [...]The patch for ada/9911 results in
 > 
 > stage1/xgcc.exe [...] /local/src/gcc/gcc/ada/raise.c
 > /usr/local/src/gcc/gcc/ada/raise.c:640:
 >  warning: function declaration isn't a prototype
 
 Oh, I can see that, sorry for the inconvenience. Weired it did not prevent the
 bootstrap on hpux yesterday.
 
 The patch below fixes it for me. Bootstrapped on i686-pc-linux-gnu, where the
 build log does not show the warning anymore.
 
 Could you please confirm if it helps on your side ?
 
 Thanks in advance,
 
 Kind Regards,
 
 Olivier
 
 
 
 2003-03-05  Olivier Hainque <hainque@act-europe.fr>
 
 	ada/9961
 	* raise.c (__gnat_Unwind_RaiseException): Add prototype to avoid
 	warning, and fix return type for the IN_RTS && !SJLJ case.
 
 
 *** raise.c.ori	Wed Mar  5 09:26:55 2003
 --- raise.c	Wed Mar  5 11:17:42 2003
 *************** __gnat_unhandled_terminate ()
 *** 88,97 ****
   }
   
   /* Below is the code related to the integration of the GCC mechanism for
 !    exception handling.  */
   
   #include "unwind.h"
   
   /* Exception Handling personality routine for Ada.
   
      ??? It is currently inspired from the one for C++, needs cleanups and
 --- 88,107 ----
   }
   
   /* Below is the code related to the integration of the GCC mechanism for
 !    exception handling. Still work in progress. */
   
   #include "unwind.h"
   
 + /* If the underlying GCC scheme for exception handling is SJLJ, the standard
 +    propagation routine (_Unwind_RaiseException) is actually renamed using a
 +    #define directive (see unwing-sjlj.c). We need a consistently named
 +    interface to import from a-except, so stubs are defined here, at the end
 +    of this file.  */
 + 
 + _Unwind_Reason_Code
 + __gnat_Unwind_RaiseException PARAMS ((struct _Unwind_Exception *));
 + 
 + 
   /* Exception Handling personality routine for Ada.
   
      ??? It is currently inspired from the one for C++, needs cleanups and
 *************** __gnat_eh_personality (version, actions,
 *** 597,606 ****
   }
   
   
 ! /* If the underlying GCC scheme for exception handling is SJLJ, the standard
 !    propagation routine (_Unwind_RaiseException) is actually renamed using a
 !    #define directive (see unwing-sjlj.c). We need a consistently named
 !    interface to import from a-except, so stubs are defined here.  */
   
   #ifdef __USING_SJLJ_EXCEPTIONS__
   
 --- 607,613 ----
   }
   
   
 ! /* Stubs for the libgcc unwinding interface, to be imported by a-except.  */ 
   
   #ifdef __USING_SJLJ_EXCEPTIONS__
   
 *************** __gnat_Unwind_RaiseException (e)
 *** 614,620 ****
   #else
   /* __USING_SJLJ_EXCEPTIONS__ not defined */
   
 ! void
   __gnat_Unwind_RaiseException (e)
        struct _Unwind_Exception *e;
   {
 --- 621,627 ----
   #else
   /* __USING_SJLJ_EXCEPTIONS__ not defined */
   
 ! _Unwind_Reason_Code
   __gnat_Unwind_RaiseException (e)
        struct _Unwind_Exception *e;
   {
 
 


             reply	other threads:[~2003-03-05 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 10:26 Olivier Hainque [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-06  0:15 billingd
2003-03-05 16:26 Olivier Hainque
2003-03-05 10:36 Olivier Hainque
2003-03-05  3:56 David.Billinghurst

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=20030305102602.18586.qmail@sources.redhat.com \
    --to=hainque@act-europe.fr \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).