Re: DWZ 0.14 released

Btw, question for gcc/binutils Any reason the work done by tools like dwz couldn't be done in the compiler or linker? Seems a bit odd to have a post-linker that optimizes the generated code, when optimizations should already be enabled. Best regards Allan On Montag, 8. März 2021 13:43:11 CET T

Re: DWZ 0.14 released

Hi Allan, On Tue, Mar 09, 2021 at 09:06:54AM +0100, Allan Sandfeld Jensen wrote: > Btw, question for gcc/binutils > > Any reason the work done by tools like dwz couldn't be done in the compiler > or > linker? Seems a bit odd to have a post-linker that optimizes the generated > code, when optim

Re: DWZ 0.14 released

Am Dienstag, 9. März 2021, 10:10:47 MEZ hat Mark Wielaard Folgendes geschrieben: > Hi Allan, > > On Tue, Mar 09, 2021 at 09:06:54AM +0100, Allan Sandfeld Jensen wrote: > > Btw, question for gcc/binutils > > > > Any reason the work done by tools like dwz couldn't be done in the compiler > > or

Re: DWZ 0.14 released

On Tue, Mar 09, 2021 at 11:38:07AM +, Hannes Domani via Dwz wrote: > Am Dienstag, 9. März 2021, 10:10:47 MEZ hat Mark Wielaard > Folgendes geschrieben: > > > Hi Allan, > > > > On Tue, Mar 09, 2021 at 09:06:54AM +0100, Allan Sandfeld Jensen wrote: > > > Btw, question for gcc/binutils > > > >

side-effect-free function

Hi, Consider some function now() which returns some kind of "current timestamp" as a simple scalar. It could be a wrapper for clock_gettime(CLOCK_MONOTONIC) which converts the timespec value to nanoseconds, or in the linux kernel one of the ktime_get* family. Then consider code like start = now(

Re: side-effect-free function

On 3/9/21 8:05 AM, Rasmus Villemoes via Gcc wrote: Hi, Consider some function now() which returns some kind of "current timestamp" as a simple scalar. It could be a wrapper for clock_gettime(CLOCK_MONOTONIC) which converts the timespec value to nanoseconds, or in the linux kernel one of the ktim