search for: physreg1

...ity &Probability) const { >> dbgs() << "OOPS " << 1.16 << "\n"; >> } >> >> This invocation works as it should (verified with gdb). But when I execute this code fragment, I get >> >> OOPS 1.140000e+00 >> OOPS %physreg1 >> OOPS 1.150000e+00 >> >> So suddenly in the machine backend, the dbgs() ostream (which is still the very same ostream as in the IfConverter, I checked the address with gdb) prints floating point numbers as if they are physical registers. Any idea what is going on or how I can f...

...;> dbgs() << "OOPS " << 1.16 << "\n"; > >> } > >> > >> This invocation works as it should (verified with gdb). But when I > execute this code fragment, I get > >> > >> OOPS 1.140000e+00 > >> OOPS %physreg1 > >> OOPS 1.150000e+00 > >> > >> So suddenly in the machine backend, the dbgs() ostream (which is still > the very same ostream as in the IfConverter, I checked the address with > gdb) prints floating point numbers as if they are physical registers. Any > idea wh...

..., const BranchProbability &Probability) const { dbgs() << "OOPS " << 1.16 << "\n"; } This invocation works as it should (verified with gdb). But when I execute this code fragment, I get OOPS 1.140000e+00 OOPS %physreg1 OOPS 1.150000e+00 So suddenly in the machine backend, the dbgs() ostream (which is still the very same ostream as in the IfConverter, I checked the address with gdb) prints floating point numbers as if they are physical registers. Any idea what is going on or how I can force floating-point numbers...

...; >> dbgs() << "OOPS " << 1.16 << "\n"; > >> } > >> > >> This invocation works as it should (verified with gdb). But when I execute this code fragment, I get > >> > >> OOPS 1.140000e+00 > >> OOPS %physreg1 > >> OOPS 1.150000e+00 > >> > >> So suddenly in the machine backend, the dbgs() ostream (which is still the very same ostream as in the IfConverter, I checked the address with gdb) prints floating point numbers as if they are physical registers. Any idea what is going on...