public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Laurent GUERBY <laurent@guerby.net>
To: gcc@gcc.gnu.org
Subject: Re: [Ada] Patch needed to boostrap Ada on x86_64 as of 20050628
Date: Wed, 29 Jun 2005 06:16:00 -0000	[thread overview]
Message-ID: <1120025762.8919.408.camel@pc.site> (raw)
In-Reply-To: <1119991811.8919.400.camel@pc.site>

flag_wrapv=1 also restores bootstrap on x86_64-linux without
needing -O0 in Makefiles.

Laurent

Index: misc.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/ada/misc.c,v
retrieving revision 1.104
diff -u -r1.104 misc.c
--- misc.c      28 Jun 2005 19:51:26 -0000      1.104
+++ misc.c      29 Jun 2005 06:12:29 -0000
@@ -339,6 +339,8 @@
   /* Uninitialized really means uninitialized in Ada.  */
   flag_zero_initialized_in_bss = 0;

+  flag_wrapv = 1;
+
   return CL_Ada;
 }



On Tue, 2005-06-28 at 22:50 +0200, Laurent GUERBY wrote:
> Ada bootstraps fine without patch on x86-linux, however
> on x86_64 bootstrap fail because of:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22212
> 
> The following patch is a workaround for it, it enables
> a full bootstrap and only 2 additional FAIL in ACATS,
> results here:
> 
> http://gcc.gnu.org/ml/gcc-testresults/2005-06/msg01693.html
> 
> Laurent
> 
> Index: gnattools/Makefile.in
> ===================================================================
> RCS file: /cvs/gcc/gcc/gnattools/Makefile.in,v
> retrieving revision 1.4
> diff -u -r1.4 Makefile.in
> --- gnattools/Makefile.in       30 Mar 2005 08:56:55 -0000      1.4
> +++ gnattools/Makefile.in       28 Jun 2005 20:45:29 -0000
> @@ -83,7 +83,7 @@
>         "CC=../../xgcc -B../../" \
>         "CFLAGS=$(CFLAGS) $(WARN_CFLAGS)" \
>         "LDFLAGS=$(LDFLAGS)" \
> -       "ADAFLAGS=$(ADAFLAGS)" \
> +       "ADAFLAGS=$(ADAFLAGS) -O0" \
>         "INCLUDES=$(INCLUDES_FOR_SUBDIR)" \
>         "ADA_INCLUDES=-I- -I../rts $(ADA_INCLUDES_FOR_SUBDIR)"\
>         "exeext=$(exeext)" \
> @@ -112,7 +112,7 @@
>  TOOLS_FLAGS_TO_PASS_NATIVE= \
>         "CC=../../xgcc -B../../" \
>         "CFLAGS=$(CFLAGS)" \
> -       "ADAFLAGS=$(ADAFLAGS)" \
> +       "ADAFLAGS=$(ADAFLAGS) -O0" \
>         "INCLUDES=$(INCLUDES_FOR_SUBDIR)" \
>         "ADA_INCLUDES=-I../rts $(ADA_INCLUDES_FOR_SUBDIR)" \
>         "exeext=$(exeext)" \
> Index: gcc/ada/Makefile.in
> ===================================================================
> RCS file: /cvs/gcc/gcc/gcc/ada/Makefile.in,v
> retrieving revision 1.118
> diff -u -r1.118 Makefile.in
> --- gcc/ada/Makefile.in 16 Jun 2005 09:00:01 -0000      1.118
> +++ gcc/ada/Makefile.in 28 Jun 2005 20:45:30 -0000
> @@ -1994,6 +1994,10 @@
>         $(CC) -c $(ALL_ADAFLAGS) $(FORCE_DEBUG_ADAFLAGS) -O1 -fno-inline
> \
>               $(ADA_INCLUDES) $< $(OUTPUT_OPTION)
> 
> +a-strfix.o  : a-strfix.adb a-strfix.ads
> +       $(CC) -c $(ALL_ADAFLAGS) $(FORCE_DEBUG_ADAFLAGS) -O0 \
> +             $(ADA_INCLUDES) $< $(OUTPUT_OPTION)
> +
>  # force debugging information on s-assert.o so that it is always
>  # possible to set breakpoint on assert failures.
> 
> 
> 
> 

      reply	other threads:[~2005-06-29  6:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 20:50 Laurent GUERBY
2005-06-29  6:16 ` Laurent GUERBY [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=1120025762.8919.408.camel@pc.site \
    --to=laurent@guerby.net \
    --cc=gcc@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).