search for: d45878

...nd myself in trouble because the crash I had disappeared with -g, so I could not debug the program. This happened because the optimizer did not remember to consider DBG_VALUEs instruction so it changed its behavior, and the bug went hiding. I then started discussing this onhttps://reviews.llvm.org/D45878, and since this is something that should be handled by all different machine passes, the immediate question is now what utility functions should be made available for common use. 1. A pass such as MachineSink.cpp must first of all remember to consider DBG_VALUEs when iterating over instructions,...

...) thoughts.] As you suspect, that's clearly a bug. LLVM's ideal behavior is that the presence of debug informations shall not affect the contents of the .text section. As you also noticed, we're not quite there yet. > > I then started discussing this on https://reviews.llvm.org/D45878, and > since this is something that should be handled by all different machine > passes, the immediate question is now what utility functions should be > made available for common use. > > 1. A pass such as MachineSink.cpp must first of all remember to consider > DBG_VALUEs when...

...yself in trouble because the crash I had disappeared with -g, so I could not debug the program. This happened because the optimizer did not remember to consider DBG_VALUEs instruction so it changed its behavior, and the bug went hiding. I then started discussing this on https://reviews.llvm.org/D45878, and since this is something that should be handled by all different machine passes, the immediate question is now what utility functions should be made available for common use. 1. A pass such as MachineSink.cpp must first of all remember to consider DBG_VALUEs when iterating over instruction...

...se the crash I had disappeared > with -g, so I could not debug the program. This happened because the > optimizer did not remember to consider DBG_VALUEs instruction so it > changed its behavior, and the bug went hiding. > > I then started discussing this on https://reviews.llvm.org/D45878, and > since this is something that should be handled by all different machine > passes, the immediate question is now what utility functions should be > made available for common use. [... snip ...] > We are discussing where to place these utility functions, and if > splice() shou...