Re: -v should print also the revision number in repo

2018-06-13 Thread U.Mutlu
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

Re: -v should print also the revision number in repo

2018-06-13 Thread U.Mutlu
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

Re: -v should print also the revision number in repo

2018-06-13 Thread Andrew Pinski
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

-v should print also the revision number in repo

2018-06-13 Thread U.Mutlu
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