* TODO: New file.
This commit is contained in:
parent
b1dba75dfe
commit
70752818b0
@ -1,3 +1,7 @@
|
|||||||
|
2008-04-02 Craig Silverstein <csilvers@google.com>
|
||||||
|
|
||||||
|
* TODO: New file.
|
||||||
|
|
||||||
2008-04-02 Ian Lance Taylor <iant@google.com>
|
2008-04-02 Ian Lance Taylor <iant@google.com>
|
||||||
|
|
||||||
* fileread.cc (File_read::find_view): Add byteshift and vshifted
|
* fileread.cc (File_read::find_view): Add byteshift and vshifted
|
||||||
|
26
gold/TODO
Normal file
26
gold/TODO
Normal file
@ -0,0 +1,26 @@
|
|||||||
|
Things that still need to be done: -*- Text -*-
|
||||||
|
|
||||||
|
o - Performance
|
||||||
|
|
||||||
|
All performance could be tuned, but one area that could be looked
|
||||||
|
at especially is performance with flags, particularly
|
||||||
|
--detect-odr-violations and --compress-debug-sections.
|
||||||
|
|
||||||
|
o - Threads
|
||||||
|
|
||||||
|
Why is the usertime when we run with threads the same (or almost
|
||||||
|
the same) as when we run without? Is it because threads spend most
|
||||||
|
of their time waiting on the same resources? On each other?
|
||||||
|
Something else?
|
||||||
|
|
||||||
|
o - ODR false positives
|
||||||
|
|
||||||
|
ODR false positives can happen when we optimize, since code in .h
|
||||||
|
files may be optimized in different ways in different compilation
|
||||||
|
units. It's possible we could fix this for real by looking at the
|
||||||
|
full debug info and using DW_TAG_inlined_subroutine in a clever way
|
||||||
|
to correct for inlining. But that would be very expensive, I
|
||||||
|
think. The easier solution is to recommend people only do
|
||||||
|
ODR-detection with -g0.
|
||||||
|
|
||||||
|
o - Better testing
|
Loading…
Reference in New Issue
Block a user