This is the mail archive of the gcc@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: Libjava failures status


Tom Tromey wrote:

>>>>>>"Bryce" == Bryce McKinlay <bryce@waitaki.otago.ac.nz> writes:
>>>>>>
>
>Bryce> It would be nice if we could avoid pessimising this too
>Bryce> much. eg given:
>
>Bryce> a = foo.a;
>Bryce> b = foo.b;
>
>Bryce> Then obviously the second load from foo can not trap.
>
>Unless foo is a field and is changed by another thread.
>Maybe this case is undefined if we haven't synchronized?
>

Right. I'm assuming it would load "foo" into a register or stack 
temporary first. As long as that happens it should be perfectly safe 
(proposed "volatile" semantics aside).

regards

Bryce.



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