public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "charlet at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/18434] [4.0/4.1 Regression] Ada: cannot build gnattools on Tru64 UNIX V5.1B
Date: Tue, 15 Nov 2005 13:51:00 -0000	[thread overview]
Message-ID: <20051115135115.14156.qmail@sourceware.org> (raw)
In-Reply-To: <bug-18434-81@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from charlet at gcc dot gnu dot org  2005-11-15 13:51 -------
Subject: Bug 18434

Author: charlet
Date: Tue Nov 15 13:51:09 2005
New Revision: 106950

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106950
Log:
2005-11-14  Robert Dewar  <dewar@adacore.com>
            Ed Schonberg  <schonberg@adacore.com>

        PR ada/18434

        * types.ads: Include All_Checks in Suppress_Array

        * checks.adb (Check_Needed): Remove kludge for a/=b rewritten as
        not(a=b), since we no longer do this rewriting, and hence it is not
        needed.
        (Elaboration_Checks_Suppressed): Add special casing to
        deal with different cases of static and dynamic elaboration checks (all
        checks does not count in the first case, but does in the second).
        (Expr_Known_Valid): Do not assume that the result of any arbitrary
        function call is valid, since this is not the case.
        (Ensure_Valid): Do not apply validity check to a real literal
        in a universal or fixed context

        * exp_ch4.adb (Expand_N_Op_Ne): Don't expand a/=b to not(a=b) for
        elementary types using the operator in standard. It is cleaner not to
        modify the programmers intent, especially in the case of
floating-point.
        (Rewrite_Comparison): Fix handling of /= (this was always wrong, but
        it did not matter because we always rewrote a/=b to not(a=b).
        (Expand_Allocator_Expression): For an allocator expression whose
nominal
        subtype is an unconstrained packed type, convert the expression to its
        actual constrained subtype.
        Implement warning for <= or >= where < or > not possible
        Fix to Vax_Float tests (too early in many routines, causing premature
        Vax_Float expansions.

        * sem_prag.adb (Analyze_Pragma, case Obsolescent): Allow this pragma
        to be used with packages and generic packages as well as with
        subprograms.
        (Suppress): Set All_Checks, but not Elaboration_Check, for case
        of pragma Suppress (All_Checks)
        (Analyze_Pragma, case Warnings): Implement first argument allowed to be
        a string literal for precise control over warnings.
        Avoid raise of pragma in case of unrecognized pragma and just return
        instead.

        * sem_prag.ads: Minor reformatting

        * switch-c.adb (Scan_Front_End_Switches): Replace "raise Bad_Switch;"
        with call to new procedure Bad_Switch. Call Scan_Pos with new parameter
        Switch. Do not handle any exception.
        Include -gnatwx as part of -gnatg (warn on redundant parens)
        Allow optional = after -gnatm
        (Scan_Front_End_Switches): The -gnatp switch sets All_Checks, but no
        longer sets Elaboration_Checks.
        Code to set warning mode moved to Sem_Warn
        so that it can be shared by pragma processing.

        * s-mastop-tru64.adb (Pop_Frame): Remove redundant parentheses in if
        statement.

        * s-taprop-solaris.adb: 
        Change some <= to =, to avoid new warning

        * a-exexda.adb, prj-proc.adb: 
        Fix obvious typo (Num_Tracebacks compared <= 0 instead of < 0)
        Fix obvious typo (Total_Errors_Detected <= 0 should be = 0)

Modified:
    trunk/gcc/ada/a-exexda.adb
    trunk/gcc/ada/checks.adb
    trunk/gcc/ada/exp_ch4.adb
    trunk/gcc/ada/prj-proc.adb
    trunk/gcc/ada/s-mastop-tru64.adb
    trunk/gcc/ada/s-taprop-solaris.adb
    trunk/gcc/ada/sem_prag.adb
    trunk/gcc/ada/sem_prag.ads
    trunk/gcc/ada/switch-c.adb
    trunk/gcc/ada/types.ads


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18434


  parent reply	other threads:[~2005-11-15 13:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18434-81@http.gcc.gnu.org/bugzilla/>
2005-10-22  9:43 ` olle at cb dot uu dot se
2005-10-22 13:40 ` bugzilla-gcc at thewrittenword dot com
2005-10-30 23:21 ` pinskia at gcc dot gnu dot org
2005-11-12 14:59 ` debian-gcc at lists dot debian dot org
2005-11-12 16:11 ` laurent at guerby dot net
2005-11-12 16:41 ` debian-gcc at lists dot debian dot org
2005-11-14 13:06 ` charlet at gcc dot gnu dot org
2005-11-14 21:34 ` guerby at gcc dot gnu dot org
2005-11-14 21:39 ` laurent at guerby dot net
2005-11-15  8:28 ` debian-gcc at lists dot debian dot org
2005-11-15 13:51 ` charlet at gcc dot gnu dot org [this message]
2005-11-15 14:08 ` charlet at gcc dot gnu dot org
2005-11-15 17:27 ` olle at cb dot uu dot se
2005-11-15 19:27 ` olle at cb dot uu dot se
2004-11-11 22:07 [Bug ada/18434] New: Cannot " gcc-bugzilla at gcc dot gnu dot org
2005-10-01 17:41 ` [Bug ada/18434] [4.0/4.1 Regression] Ada: cannot " laurent at guerby dot net

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=20051115135115.14156.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).