U.Mutlu wrote on 06/13/2018 10:26 PM:
Andrew Pinski wrote on 06/13/2018 10:06 PM:
On Wednesday, June 13, 2018, U.Mutlu mailto:u...@mutluit.com>>
wrote:
Hi,
currently -v (ie. gcc -v) prints these data:
gcc version 9.0.0 20180613 (experimental) (GCC)
It would be nice, when buil
Andrew Pinski wrote on 06/13/2018 10:06 PM:
On Wednesday, June 13, 2018, U.Mutlu mailto:u...@mutluit.com>>
wrote:
Hi,
currently -v (ie. gcc -v) prints these data:
gcc version 9.0.0 20180613 (experimental) (GCC)
It would be nice, when building from a repository that then the re
On Wednesday, June 13, 2018, U.Mutlu wrote:
> Hi,
>
> currently -v (ie. gcc -v) prints these data:
>
> gcc version 9.0.0 20180613 (experimental) (GCC)
>
> It would be nice, when building from a repository that then the resulting
> target should contain also the revision number (for example "r2615
Hi,
currently -v (ie. gcc -v) prints these data:
gcc version 9.0.0 20180613 (experimental) (GCC)
It would be nice, when building from a repository that then the resulting
target should contain also the revision number (for example "r261543")
of the underlying repository, so that gcc -v then pri