From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 72DE43954439; Sun, 15 Mar 2020 19:30:12 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 72DE43954439
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1584300612;
 bh=TEpVRJCzuhLR5ldDvm0fAdxO62sjNHdSvVkeFT9Xhkw=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=b0m8I+vWDRKYzvF4nNvFBcPZjUJWpkq9jmgS97XEsS8ufNV11weaJMQosleJOoAdf
 m4EkXrv+6/OPs5Yqtv31+wwdT9E7+UlmQRPFP8ZQZR0l1BqDIppZDNSiUpyN6N4Lqz
 1YL4I1TWn8tfWiECzlguC9aeA8yKh/GRIK/BS8sA=
From: "frederic.recoules@univ-grenoble-alpes.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93903] invalid input constraint in __asm__
Date: Sun, 15 Mar 2020 19:30:12 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: frederic.recoules@univ-grenoble-alpes.fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93903-4-4501EuN8Lk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93903-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93903-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <http://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Mar 2020 19:30:12 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93903

Fr=C3=A9d=C3=A9ric Recoules <frederic.recoules@univ-grenoble-alpes.fr> chan=
ged:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |frederic.recoules@univ-gren
                   |                            |oble-alpes.fr

--- Comment #2 from Fr=C3=A9d=C3=A9ric Recoules <frederic.recoules@univ-gre=
noble-alpes.fr> ---
(In reply to Fr=C3=A9d=C3=A9ric Recoules from comment #1)
> I am pretty sure the error comes from the space you left in "r ".
> Yet, in the "Simple-Constraints" documentation, it is said that space are
> ignored
> to allow visual alignment but, in fact, I realized a while ago it generat=
es
> an error.
>=20
> I think it would not be a big change to either update the documentation at
> https://gcc.gnu.org/onlinedocs/gcc/Simple-Constraints.html#Simple-
> Constraints or to make the parser ignore the blank.

I read me again and see how my comment was useless but, I really wanted to
help.
In fact I found that space are authorized for output but not for input.

In the file stmt.c:=20

In the function parse_input_constraint, the default case starts with:

if (!ISALPHA (*p))
            break;

So it just exits the switch and continue, while the default case of
parse_input_constraint starts with:=20

if (! ISALPHA (constraint[j]))
          {
            error ("invalid punctuation %qc in constraint", constraint[j]);
            return false;
          }

Yet, I would add in the switch for both:

case ' ':
  break;=