This is the mail archive of the binutils@sourceware.org mailing list for the binutils 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: PREVAILING_DEF_IRONLY_EXP

From: Cary Coutant <ccoutant at google dot com>
To: Rafael Ávila de Espíndola <respindola at mozilla dot com>
Cc: binutils at sourceware dot org
Date: Wed, 23 Mar 2011 15:27:28 -0700
Subject: Re: PREVAILING_DEF_IRONLY_EXP
References: <4D82EA43.2050606@mozilla.com>

> Why is PREVAILING_DEF_IRONLY_EXP needed?
> ...
> Is there a case I am missing? Maybe a symbol that is defined in comdat in
> one file but can have an undefined reference without accompanying definition
> in another!?! If not, I would propose changing the text to

This is pretty much the reason. We want to distinguish between symbols
that are truly referenced from outside the IR and those that are
merely exported, so that the compiler can only drop the optimized-away
symbols without assuming that all code in the app was produced by that
compiler, using the same conventions.

See:

   http://sourceware.org/ml/binutils/2010-12/msg00040.html

and follow-ups for the reasoning.

-cary

References:
- PREVAILING_DEF_IRONLY_EXP
  - From: Rafael Ávila de Espíndola

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