summaryrefslogtreecommitdiffstats
path: root/binutils-2.25/gold/TODO
diff options
context:
space:
mode:
authorAndrew Hsieh <andrewhsieh@google.com>2014-06-13 12:38:00 -0700
committerAndrew Hsieh <andrewhsieh@google.com>2014-06-13 12:38:00 -0700
commit54f1b3cf509cd889905287cb8ce6c5ae33911a21 (patch)
treee39b1a7fa04db86a8215b7f9d4656d74e394aec0 /binutils-2.25/gold/TODO
parent2a6558a8ecfb81d75215b4ec7dc61113e12cfd5f (diff)
downloadtoolchain_binutils-54f1b3cf509cd889905287cb8ce6c5ae33911a21.tar.gz
toolchain_binutils-54f1b3cf509cd889905287cb8ce6c5ae33911a21.tar.bz2
toolchain_binutils-54f1b3cf509cd889905287cb8ce6c5ae33911a21.zip
Add upstream binutils-2.25 snapshot 4/4 2014
For MIPS -mmsa support Change-Id: I08c4f002fa7b33dec85ed75956e6ab551bb03c96
Diffstat (limited to 'binutils-2.25/gold/TODO')
-rw-r--r--binutils-2.25/gold/TODO26
1 files changed, 26 insertions, 0 deletions
diff --git a/binutils-2.25/gold/TODO b/binutils-2.25/gold/TODO
new file mode 100644
index 00000000..b85df975
--- /dev/null
+++ b/binutils-2.25/gold/TODO
@@ -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