llvm dev - Jun 2013 - [LLVMdev] Contants generation

Hi again,

Actually, I've just been looking at the existing code and the ARM
solution may be over-complicated for this situation.

You should be able to override EmitConstantPool directly, or possibly
even just override getSectionForConstantKind in
X86LinuxTargetObjectFile (and perhaps others) to return .text.

Tim.

That what I actually did now, locally in the code.
But I still see the " movabsq"

	.text
	.align	8, 0x90
.LCPI0_0:
	.quad	4606281698874543309     # double 0.9
.LCPI0_1:
	.quad	4631147119616759172     # double 42.2794408
.LCPI0_2:
	.long	1065353216              # float 1
	.zero	4
...
	movabsq	$.LCPI0_1, %rax         # encoding: [0x48,0xb8,A,A,A,A,A,A,A,A]
                                        #   fixup A - offset: 2, value:
.LCPI0_1, kind: FK_Data_8
	vbroadcastsd	(%rax), %ymm0   # encoding: [0xc4,0xe2,0x7d,0x19,0x00] 

Actually, I'm looking for a flag that can say that the whole constants pool
is in code section.

-  Elena


-----Original Message-----
From: Tim Northover [mailto:t.p.northover at gmail.com] 
Sent: Tuesday, June 25, 2013 15:08
To: Demikhovsky, Elena
Cc: llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] Contants generation

Hi again,

Actually, I've just been looking at the existing code and the ARM solution
may be over-complicated for this situation.

You should be able to override EmitConstantPool directly, or possibly even just
override getSectionForConstantKind in X86LinuxTargetObjectFile (and perhaps
others) to return .text.

Tim.
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

> But I still see the " movabsq"
Ah yes, I'd forgotten that the instruction sequence is still largely
decided in X86ISelLowering.cpp.

You should start by tweaking the LowerConstantPool function. But that
seems to cause an ISel failure that you'll have to investigate
(something isn't expecting to have to deal with RIP relative accesses
in Large code model).

Tim.