This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Bug debug/13974] [3.4/3.5 regression] bad line marker in debug info


On Sun, Mar 14, 2004 at 11:12:43AM +0100, Jan Hubicka wrote:
> Code motion in loop optimizer, gcse, profiling and similar code emitting
> to BB headers/footers and such.  You are quite right that once you
> choose particular instruction in the middle of basic block to emit
> something around, you usually want to have it associated with that
> instruction in local optimizers.

Remember what these locators are used for - as far as I know the only
correct use is for debug information and debugging dumps.  So what do
we gain from not giving them a location - not very much.

> The questional thing is what to do when instrucitons already have
> locators set (ie you are doing code motion and such), but if it really
> seems to be sane to just flip the API other way around, I can rename the
> emit functions *_noloc and update the uses in CFG, loop and friends.

Well, that's what I'd like to see.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]