Re: Assuming types for PC

["Maciej W. Rozycki" <macro at codesourcery dot com>]

On Mon, 10 Jun 2013, Mark Kettenis wrote:

> > >> If PC should not have a fixed type, i think it would be best to remove
> > >> this check.
> > >
> > > Please don't.
> > 
> > Is there a more elaborate reasoning for not removing this check?
> 
> It serves a s a reminder that there are still issues to fix for some
> of the architectures.  Perhaps we should add a KFAIL for architectures
> that have the 32-bit/64-bit identity crisis I mentioned.  But other
> architectures should just change the PC type to "code_ptr".

 That's not going to work for cases like MIPS n32 (the original cause of 
the failure) that is a 64-bit ILP32 ABI.  There the PC like all the 
general registers is 64-bit wide and the pointer type is 32-bit, which is 
narrower than a register.  This is solved by using the "long long" type as 
the register type (that type is specified by the ABI to occupy a single 
hardware register; also stack frames use slots of this size to store 
registers).

 I think it is important to let the user access the full width of the PC 
both for writes and -- more importantly -- for reads (as in: why did my 
program crash, did it jump to an odd place?), as this lets the user do 
with GDB what hardware permits.  There is nothing in hardware that 
prevents one from writing an out-of-valid ABI address space value to the 
PC at a program's runtime (neither on Linux nor on bare iron) when 
executing an n32 program.  I think GDB should not stand in a user's way 
and should allow the same to be done via ptrace(2) or RSP.

 Overall I think the test is too strict.  If you think the use of "long 
long" is unfortunate for the PC, then an artificial type might be created 
internally within GDB specifically for the PC, similarly to what we do 
e.g. for IEEE 754 data types and floating-point registers in some cases.

 Joel, I hope this serves your:

> Maybe another way of saying this would be "it should, unless proven 
> otherwise". In your case, it sounds like you are saying "it might", or 
> perhaps "some platforms don't", to which Mark is replying "show me" 
> (backed by the architecture manuals) :-) :-) :-).

request for a justification...

 ... ah, you've asked for a manual too -- here's one then:

http://techpubs.sgi.com/library/manuals/2000/007-2816-004/pdf/007-2816-004.pdf

;)

  Maciej