--- Comment #5 from Martin Liška <marxin at gcc dot> ---
(In reply to Arseny Solokha from comment #4)
> (In reply to Martin Liška from comment #3)
> > For next PRs,
> > please output content of gcc -v so that we can identify a single commit.
> Sure, but how can this possibly help to identify a commit? I dont' have a
> revision in the gcc -v output. I believe snapshot announcements[1] are those
> authoritative sources that list revisions from which the corresponding
> snapshots has been generated. Am I missing something?
> [1]

Yes, but I was thinking that you are using a nighly builds from trunk?
Even my distribution release comes with a revision:

$ gcc -v
Using built-in specs.
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
--enable-offload-targets=hsa,nvptx-none=/usr/nvptx-none, --without-cuda-driver
--enable-checking=release --disable-werror
--with-gxx-include-dir=/usr/include/c++/7 --enable-ssp --disable-libssp
--disable-libvtv --disable-libcc1 --enable-plugin
--with-bugurl= --with-pkgversion='SUSE Linux'
--with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --with-gcc-major-version-only
--enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function
--program-suffix=-7 --without-system-libunwind --enable-multilib
--with-arch-32=x86-64 --with-tune=generic --build=x86_64-suse-linux
Thread model: posix
gcc version 7.1.1 20170629 [gcc-7-branch revision 249772] (SUSE Linux)

Reply via email to