diff options
author | Ian Lance Taylor <ian@airs.com> | 2008-04-03 00:33:37 +0000 |
---|---|---|
committer | Ian Lance Taylor <ian@airs.com> | 2008-04-03 00:33:37 +0000 |
commit | 70752818b006aa0a0758f076f7a0a24288e37676 (patch) | |
tree | 332d7e19b771ec2c481361bf4d5c0d27d16f967f /gold/TODO | |
parent | b1dba75dfe51f283f97f200dd8090a55d05eb157 (diff) | |
download | gdb-70752818b006aa0a0758f076f7a0a24288e37676.zip gdb-70752818b006aa0a0758f076f7a0a24288e37676.tar.gz gdb-70752818b006aa0a0758f076f7a0a24288e37676.tar.bz2 |
* TODO: New file.
Diffstat (limited to 'gold/TODO')
-rw-r--r-- | gold/TODO | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/gold/TODO b/gold/TODO new file mode 100644 index 0000000..b85df97 --- /dev/null +++ b/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 |