[llvm-dev] why do undefined globals end up in .data instead of .bss?

[Tobias Edler von Koch via llvm-dev]

On 04/24/2017 01:55 PM, Andrew Kelley via llvm-dev wrote:
> I see, thanks. Would a patch be welcome which changed this behavior? 
> Or I suppose I could emit zeroinitializer instead of undef. But it 
> seems like undef is the more correct value.

Are you producing these undef values yourself (in a pass/fronted)? Can 
you elaborate a little on why you think "undef" is the correct value? 
Inside LLVM, undef essentially means "any value we choose". The language 
reference has a section on this. It would be entirely correct if we 
emitted all 1s instead of all 0s for undef. If you really want it to be 
.bss, zeroinitializer seems to be the better choice.

Tobias

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170425/d1bf905e/attachment.html>