Memory Handling

2020-07-29 Thread y2s1982 via Gcc
o through everything > you have such comments on, and instead create ompd-info-generate.c > to contain some macros that in the end will store the offsetof value in the > output and then on the libgompd.so.1 part read that back. > > Jakub > > I made some changes to how I wa

Re: Problem with equivalent memory handling

2010-10-26 Thread Ian Lance Taylor
Jeff Law writes: >> If >> there is any register pressure, B is going to go onto the stack or is >> going to force something else onto the stack. > Not today, which is the problem. Well, I was implicitly anding in the clause "if the compiler were correct." Ian

Re: Problem with equivalent memory handling

2010-10-26 Thread Jeff Law
On 10/19/10 14:42, Ian Lance Taylor wrote: Jeff Law writes: Reload has the ability to replace a pseudo with its equivalent memory location. This is fine and good. Imagine: 1. We have a pseudo (call is pseudo A) with a read-only memory equivalent. Pseudo A does not get a hard reg 2.

Re: Problem with equivalent memory handling

2010-10-19 Thread Ian Lance Taylor
Jeff Law writes: > Reload has the ability to replace a pseudo with its equivalent memory > location. This is fine and good. > > Imagine: > > 1. We have a pseudo (call is pseudo A) with a read-only memory > equivalent. Pseudo A does not get a hard reg > > 2. Pseudo A crosses a call (because

Problem with equivalent memory handling

2010-10-19 Thread Jeff Law
Looking for advice here -- while I haven't seen this bug trigger in the mainline, it triggers with the range splitting code I've been working on. Reload has the ability to replace a pseudo with its equivalent memory location. This is fine and good. Imagine: 1. We have a pseudo (call is