Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Apr 2013 21:22:44 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        Dimitry Andric <dim@FreeBSD.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD ports <freebsd-ports@freebsd.org>, Jan Beich <jbeich@tormail.org>
Subject:   Re: CURRENT (r249438): (devel/libiconv)./unistd.h:686:5: error: invalid token at start of a preprocessor expression : #if @GNULIB_EUIDACCESS@
Message-ID:  <1366140164.1505.2.camel@thor.walstatt.dyndns.org>
In-Reply-To: <E15F2208-0A57-4C40-B7B0-FEA7953500AD@FreeBSD.org>
References:  <1365877246.2093.20.camel@thor.walstatt.dyndns.org> <1URs5b-000B9U-A2@internal.tormail.org> <E15F2208-0A57-4C40-B7B0-FEA7953500AD@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-+JNEwKYMXXQyvXjb8Vxe
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Tue, 2013-04-16 at 20:58 +0200, Dimitry Andric wrote:
> On Apr 16, 2013, at 00:42, Jan Beich <jbeich@tormail.org> wrote:
> > "O. Hartmann" <ohartman@zedat.fu-berlin.de> writes:
> >> ./unistd.h:694:5: error: invalid token at start of a preprocessor
> >> expression
> >> #if @GNULIB_EUIDACCESS@
> >>    ^
> >> 1 error generated.
> >=20
> > Maybe -O3 overoptimizes regex in libc e.g.,
> >=20
> > $ echo '#if @GNULIB_EUIDACCESS@' | sed 's/@GNULIB_EUIDACCESS@/0/'
> > #if @GNULIB_EUIDACCESS@
> >=20
> > $ echo 'aaaaaaaaaaaaaaaaxxxaaaa' | sed 's/aaaaaaaaaaaaxxxaaaa//'
> > aaaaaaaaaaaaaaaaxxxaaaa
>=20
> How did you arrive at this result?  I have recompiled both libc and sed
> with -O3, but it works just fine here.  Maybe -march=3Dnative is the clue=
,
> so which kind of CPU do you have?  To see what CPU llvm detects, try:
>=20
>   tblgen -version | grep CPU
>=20
> Note that -O3 turns on clang's vectorizer, so you might have run into an
> optimizer bug, or some kind of undefined behavior which now falls over.
>=20
> -Dimitry
>=20
 tblgen -version | grep CPU:

Host CPU: penryn (host A)
Host CPU: core-avx-i (host B)
Host CPU: corei7-avx (host C)

and the problem occurs on all of those boxes running most recent FreeBSD
10.0-CURRENT with CLANG 3.3


--=-+JNEwKYMXXQyvXjb8Vxe
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAABAgAGBQJRbaUEAAoJEOgBcD7A/5N80zoIANwvx2NHWhqz7ElKbxTqolpU
dJatrIJxdlBgYosrV6oFmN4z4SdViNuKUS1rDD7/SkvBnrdNlETBLJlVnG84+VsY
ydrXZ2CvZRj3jk7LfvT7M/K741ZEQtN7JyZj81Lk5jnGycUmr9AIwyt3GRciTTWk
pySq9fkcmT3kk3atihoT6C4ko+CZxoyaOSEPOzSKOOxwO9aGKjfSH7offTi22vj5
dTaVhhEE5LVvB4NsJVIIkI17o1EllKMUQNh2F63FITXpdgnNXN6FV2/rXNBwLV97
SVvbc+6RPVF4pXCtKir/a4km4ZKLpwaN16wJ6wlt2M80M+ssr0WemdYhXcg6AaQ=
=euec
-----END PGP SIGNATURE-----

--=-+JNEwKYMXXQyvXjb8Vxe--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1366140164.1505.2.camel>