Re: F34 Change proposal: Debug Info Standardization (from DWZ to -fdebug-types-section) (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Fri, 2020-09-25 at 17:18 +0200, Florian Weimer wrote:
> * Robbie Harwood:
> > Jan Kratochvil <jan.kratochvil@xxxxxxxxxx> writes:
> > > So why is Google using it for everything?
> > 
> > If I could eliminate one bad thought pattern in software design it would
> > probably be this one.
> > 
> > In brief: you are not Google, nor are you Facebook, nor Amazon.  Your
> > problems are not their problems.  Your use case is not their use case.
> > Plenty of things work great for them that will work terribly for you.
> > 
> > So saying "Google does it" (or similar) is *not* a good argument.
> 
> Agreed, especially since we know that e.g. Google's use of C++ does not
> align well with how many other programmers use the language.

The Google engineers responsible for their internal build system don't
make it a secret. They use debug-types combined with [out of .o file]
split-dwarf[=split]. But they also admit that it is for a specialized
use case that might only makes sense if you have a central build system
that farms out different parts of the build/compile/link steps to
different machines.

   (for Google) - a distributed build system that is trying to avoid
   moving more bytes than it must to one machine to run the link step.
   So not having to ship all the DWARF bytes to one machine for
   interactive debugging (pulling down from a distributed file system
   only the needed .dwo files during debugging - not all of them) - or
   at least being able to ship all the .dwo files to one machine to
   make a .dwp, and ship all the .o files to another machine for the
   link.

It is certainly a clever setup and makes sense if your build bottleneck
is sending files around between different machines. But I don't think
this is the generic Fedora packager or developer use case.

Cheers,

Mark
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux