public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [patch] Disable Ada front-end checking in release mode
Date: Fri, 11 Jan 2013 10:33:00 -0000	[thread overview]
Message-ID: <CAFiYyc0zgMEWVukzCN5jE+QMJqr6ARvfgN-uH1hyUKujo2i3Hw@mail.gmail.com> (raw)
In-Reply-To: <1477074.PI8pod8Vd6@polaris>

On Fri, Jan 11, 2013 at 10:08 AM, Eric Botcazou <ebotcazou@adacore.com> wrote:
> Hi,
>
> the Ada part of the Ada front-end is compiled with -gnata, which boils down to
> a form of dynamic type checking for the AST, i.e. something roughly equivalent
> to Tree checking for the front-ends of the C family of compilers.  This patch
> aligns the Ada compiler with them by disabling it in --enable-checking=release
> mode.  Issues flagged by this checking are usually benign on release branches
> and gigi has a slew of gcc_assert's that stop the compiler in serious cases.
>
> Bootstrapped on x86_64-suse-linux (w and w/o --enable-checking=release), OK
> for the mainline?

Ok.

Thanks,
Richard.

>
> 2013-01-11  Eric Botcazou  <ebotcazou@adacore.com>
>
>         * Makefile.tpl (BOOT_ADAFLAGS): Remove -gnata.
>         * Makefile.in: Regenerate.
>
>
> gcc/
> 2013-01-11  Eric Botcazou  <ebotcazou@adacore.com>
>
>         * configure.ac (Tree checking): Set TREECHECKING to yes if enabled.
>         Substitute TREECHECKING.
>         * configure: Regenerate.
>         * Makefile.in (TREECHECKING): New.
>
>
> gcc/ada/
> 2013-01-11  Eric Botcazou  <ebotcazou@adacore.com>
>
>         * gcc-interface/Make-lang.in (COMMON_ADAFLAGS): Remove -gnata.
>         (CHECKING_ADAFLAGS): New.
>         (ALL_ADAFLAGS): Include CHECKING_ADAFLAGS.
>
>
> --
> Eric Botcazou

      reply	other threads:[~2013-01-11 10:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11  9:11 Eric Botcazou
2013-01-11 10:33 ` Richard Biener [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=CAFiYyc0zgMEWVukzCN5jE+QMJqr6ARvfgN-uH1hyUKujo2i3Hw@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@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).