* -v should print also the revision number in repo
@ 2018-06-13 20:07 U.Mutlu
2018-06-13 20:09 ` Andrew Pinski
0 siblings, 1 reply; 4+ messages in thread
From: U.Mutlu @ 2018-06-13 20:07 UTC (permalink / raw)
To: gcc
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 prints this info as well.
Maybe the respective revision nbr of the repository used (svn, git, ...),
or perhaps better: a new generic solution with a unique & common rev-nbr
for all repos (and non-repos): a new file with rev-info in the repo-root
could do the trick, IMO...
Thx
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: -v should print also the revision number in repo
2018-06-13 20:07 -v should print also the revision number in repo U.Mutlu
@ 2018-06-13 20:09 ` Andrew Pinski
2018-06-13 20:26 ` U.Mutlu
0 siblings, 1 reply; 4+ messages in thread
From: Andrew Pinski @ 2018-06-13 20:09 UTC (permalink / raw)
To: U.Mutlu; +Cc: gcc
On Wednesday, June 13, 2018, U.Mutlu <um@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 resulting
> target should contain also the revision number (for example "r261543")
> of the underlying repository, so that gcc -v then prints this info as well.
>
> Maybe the respective revision nbr of the repository used (svn, git, ...),
> or perhaps better: a new generic solution with a unique & common rev-nbr
> for all repos (and non-repos): a new file with rev-info in the repo-root
> could do the trick, IMO...
If you use contrib/gcc_update, it will place the right thing in the needed
file and will display the revision.
Thanks,
Andrew
>
> Thx
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: -v should print also the revision number in repo
2018-06-13 20:09 ` Andrew Pinski
@ 2018-06-13 20:26 ` U.Mutlu
2018-06-13 22:43 ` U.Mutlu
0 siblings, 1 reply; 4+ messages in thread
From: U.Mutlu @ 2018-06-13 20:26 UTC (permalink / raw)
To: gcc; +Cc: Andrew Pinski
Andrew Pinski wrote on 06/13/2018 10:06 PM:
> On Wednesday, June 13, 2018, U.Mutlu <um@mutluit.com <mailto:um@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 resulting
> target should contain also the revision number (for example "r261543")
> of the underlying repository, so that gcc -v then prints this info as well.
>
> Maybe the respective revision nbr of the repository used (svn, git, ...),
> or perhaps better: a new generic solution with a unique & common rev-nbr
> for all repos (and non-repos): a new file with rev-info in the repo-root
> could do the trick, IMO...
>
>
> If you use contrib/gcc_update, it will place the right thing in the needed
> file and will display the revision.
Ah, cool! Will try it out, thx.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: -v should print also the revision number in repo
2018-06-13 20:26 ` U.Mutlu
@ 2018-06-13 22:43 ` U.Mutlu
0 siblings, 0 replies; 4+ messages in thread
From: U.Mutlu @ 2018-06-13 22:43 UTC (permalink / raw)
To: Andrew Pinski; +Cc: gcc
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 <um@mutluit.com <mailto:um@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 resulting
>> target should contain also the revision number (for example "r261543")
>> of the underlying repository, so that gcc -v then prints this info as well.
>>
>> Maybe the respective revision nbr of the repository used (svn, git, ...),
>> or perhaps better: a new generic solution with a unique & common rev-nbr
>> for all repos (and non-repos): a new file with rev-info in the repo-root
>> could do the trick, IMO...
>>
>>
>> If you use contrib/gcc_update, it will place the right thing in the needed
>> file and will display the revision.
>
> Ah, cool! Will try it out, thx.
Ok, it worked like a charm:
gcc version 9.0.0 20180613 (experimental) [trunk revision 261570] (GCC)
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-06-13 22:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-13 20:07 -v should print also the revision number in repo U.Mutlu
2018-06-13 20:09 ` Andrew Pinski
2018-06-13 20:26 ` U.Mutlu
2018-06-13 22:43 ` U.Mutlu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).