[sr #110353] AC_OPENMP can clobber files named `mp` or `penmp` in the source directory

--8323329-1649760492-1772071525=:318523
Content-Type: TEXT/plain; CHARSET=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Disposition: inline

Follow-up Comment #4, sr #110353 (group autoconf):=0A=0AYeah, I'm not surpr=
ised.  This is the list of options AC_OPENMP tries:=0A=0A=0A-fopenmp=0A-xop=
enmp=0A-openmp=0A-mp=0A-omp=0A-qsmp=3Domp=0A-homp=0A-Popenmp=0A--openmp=0A=
=0A=0ABecause of the way conglomerated short options work, all but three of=
 those=0Aare at risk of being interpreted as -o penmp or -o mp, possibly wi=
th some=0Aother junk option, by _any_ compiler that _doesn't_ recognize the=
 entire token=0Aas a long option.  There's nothing we can do to prevent tha=
t.=0A=0AIf the version of AC_OPENMP _in Autoconf proper_ -- not a clone fro=
m the=0Aautoconf archive -- can, under some circumstances, either leave a f=
ile named=0A"penmp" or "mp" behind after execution (regardless of the outco=
me of the=0Atest), or cause an existing file with one of those names to get=
 destroyed,=0Aplease file a new bug report about that, but that's the best =
we can do.=0A=0A=0A    ____________________________________________________=
___=0A=0AReply to this item at:=0A=0A  <https://savannah.gnu.org/support/?1=
10353>=0A=0A_______________________________________________=0AMessage sent =
via Savannah=0Ahttps://savannah.gnu.org/=0A
--8323329-1649760492-1772071525=:318523
Content-Type: APPLICATION/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaZ+qZQAKCRCqLAuaBUf3
TnAVAQDvdZme95LooZXo6hID6zzZsBwik7C8bQIGsg0cijwAXwD/Y9/4TsKY7xKw
uURQR+G0EpwUtreHX2s5W4zZTCbBEAs=
=ZJWZ
-----END PGP SIGNATURE-----

--8323329-1649760492-1772071525=:318523--