[PATCH] Consider offset in global variables during lowering in NVPTX.

[Samuel Antao]

My understanding is that the backend clients (e.g. clang) may request a given relocation model. If nothing else is specified by the user, this relocation model would be 'static'. I thought relocation model = default would map to one of the supported relocation models, and static would be what makes more sense for NVPTX. This would however drive some optimized behaviors in the combiner causing the issue reported here to be exposed.

The diff above discards any relocation model information specified by the client.

Let me know any other comments you may have,

Thanks!
Samuel


http://reviews.llvm.org/D9940

EMAIL PREFERENCES
  http://reviews.llvm.org/settings/panel/emailpreferences/