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: signed is undefined and has been since 1992 (in GCC)


Robert Dewar <dewar@adacore.com> writes:

| Gabriel Dos Reis wrote:
| 
| > The issue here is whether if the hardware consistently display a
| > semantics, GCC should not allow access to that consistent semantics
| > under the name that "the standard says it is undefined behaviour".
| > Consider the case of converting a void* to a F*, where F is a function
| > type.
| 
| Well the "hardware consistently displaying a semantics" is not so
| cut and dried as you think (consider the loop instruction and other
| arithmetic on the x86 for instance in the context of generating code
| for loops).

Please do remember that this is hardware dependent.  If you have
problems with x86, it does not mean you have the same witha PPC or a
Sparc. 

-- Gaby


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