On Mon, May 10, 2010 at 05:20:22PM +0100, Dave Korn wrote:
> On 10/05/2010 17:16, Dave Korn wrote:
> > On 10/05/2010 16:19, Jack Howarth wrote:
> >
> >> Compiler executable checksum: c54eb6db87684e4d5a5bb9ad02c2b2c4
> >> 20081222_1.c:16: error: 'EXT_x' aliased to undefined symbol 'INT_x'
>
> >
On 10/05/2010 17:16, Dave Korn wrote:
> On 10/05/2010 16:19, Jack Howarth wrote:
>
>> Compiler executable checksum: c54eb6db87684e4d5a5bb9ad02c2b2c4
>> 20081222_1.c:16: error: 'EXT_x' aliased to undefined symbol 'INT_x'
> The error comes from finish_aliases_1 in varasm.c, where it is suppressed
On 10/05/2010 16:19, Jack Howarth wrote:
> Compiler executable checksum: c54eb6db87684e4d5a5bb9ad02c2b2c4
> 20081222_1.c:16: error: 'EXT_x' aliased to undefined symbol 'INT_x'
>
> which I assume means this error message is coming from the compiler and not
> the linker. So it still unclear to me i
On Mon, May 10, 2010 at 04:17:26PM +0100, Dave Korn wrote:
> On 10/05/2010 14:30, Jack Howarth wrote:
>
> > Are there any standards in effect which would dictate that
> > the alias of a hidden function is valid?
>
> Visiblity doesn't apply to functions, it applies to symbols. Symbols are
> te
On 10/05/2010 14:30, Jack Howarth wrote:
> Are there any standards in effect which would dictate that
> the alias of a hidden function is valid?
Visiblity doesn't apply to functions, it applies to symbols. Symbols are
textual names with a linked value that exist in object files. The compiler
