llvm dev - Jun 2013 - [LLVMdev] LLVM/Clang research questions

Greetings,

First, my apologies if I have incorrectly used any of these lists.

I'm sending this email in order to get some help on where in the
codebases for LLVM and/or Clang I should be looking in order to
accomplish the following:

- create 4 additional memory segment
- - 2 to be used as "additional stacks"
- - 2 to be used as "additional heaps"

- modify the stack frame and stack pointer registers (in order to make
use of the 2 "additional stacks")

- modify segment descriptors, as needed, to support reads/writes to the
additional segments

- modify which stack variables go to which of the three stacks
- - same for heaps

Thank you.

Sincerely,

~Brent Roth~

Hi Brent, LLVM supports segmented stacks, I suggest you do a case
insensitive grep for segmented.stack in the source code (the . is
to match any character).

Ciao, Duncan.

On 03/06/13 00:35, Brent Gregory Roth wrote:
> Greetings,
>
> First, my apologies if I have incorrectly used any of these lists.
>
> I'm sending this email in order to get some help on where in the
> codebases for LLVM and/or Clang I should be looking in order to
> accomplish the following:
>
> - create 4 additional memory segment
> - - 2 to be used as "additional stacks"
> - - 2 to be used as "additional heaps"
>
> - modify the stack frame and stack pointer registers (in order to make
> use of the 2 "additional stacks")
>
> - modify segment descriptors, as needed, to support reads/writes to the
> additional segments
>
> - modify which stack variables go to which of the three stacks
> - - same for heaps
>
> Thank you.
>
> Sincerely,
>
> ~Brent Roth~
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>

Hi Duncan,

Are the segmented stacks actually on separate memory segments? My intended
purpose for placing different datatypes on separate stacks is such that
memory accesses to one datatype won't be allowed to overflow to another
datatype.

If they aren't, in fact, on separate memory segments, are you aware of a
way to place a non-readable/-writable segment in between two other stack
segments?

Thanks,

~Brent Roth~

On Mon, Jun 3, 2013 at 3:20 AM, Duncan Sands <baldrick at free.fr> wrote:
> Hi Brent, LLVM supports segmented stacks, I suggest you do a case
> insensitive grep for segmented.stack in the source code (the . is
> to match any character).
>
> Ciao, Duncan.
>
>
> On 03/06/13 00:35, Brent Gregory Roth wrote:
>
>> Greetings,
>>
>> First, my apologies if I have incorrectly used any of these lists.
>>
>> I'm sending this email in order to get some help on where in the
>> codebases for LLVM and/or Clang I should be looking in order to
>> accomplish the following:
>>
>> - create 4 additional memory segment
>> - - 2 to be used as "additional stacks"
>> - - 2 to be used as "additional heaps"
>>
>> - modify the stack frame and stack pointer registers (in order to make
>> use of the 2 "additional stacks")
>>
>> - modify segment descriptors, as needed, to support reads/writes to the
>> additional segments
>>
>> - modify which stack variables go to which of the three stacks
>> - - same for heaps
>>
>> Thank you.
>>
>> Sincerely,
>>
>> ~Brent Roth~
>> ______________________________**_________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>>
http://lists.cs.uiuc.edu/**mailman/listinfo/llvmdev<http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev>
>>
>>
> ______________________________**_________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>
http://lists.cs.uiuc.edu/**mailman/listinfo/llvmdev<http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20130603/f868423e/attachment.html>