Displaying 20 results from an estimated 30000 matches similar to: "plugin: has_many_booleans"
2015 Jan 29
0
[LLVMdev] IR extension proposal: bitset constants
On Thu, Jan 29, 2015 at 12:16:58PM +0000, Renato Golin wrote:
> On 29 Jan 2015 11:36, "Sean Silva" <chisophugis at gmail.com> wrote:
> >
> >
> >
> > On Thu, Jan 29, 2015 at 12:53 AM, Renato Golin <renato.golin at linaro.org>
> wrote:
> >>
> >> So, bitset would be a property that means : globals with the same name
> will
2015 Jan 29
3
[LLVMdev] IR extension proposal: bitset constants
So, bitset would be a property that means : globals with the same name will
append on a string of bits in the order in which they appear, and it's the
job of the front end to make sure the correct order is followed in every
unit, so that linking does the right job in every corner case?
Could that be used for efficient global boolean flags, like LLVM's options?
Even if you don't need
2015 Jan 29
2
[LLVMdev] IR extension proposal: bitset constants
On 29 Jan 2015 11:36, "Sean Silva" <chisophugis at gmail.com> wrote:
>
>
>
> On Thu, Jan 29, 2015 at 12:53 AM, Renato Golin <renato.golin at linaro.org>
wrote:
>>
>> So, bitset would be a property that means : globals with the same name
will append on a string of bits in the order in which they appear, and it's
the job of the front end to make sure
2015 Jan 28
3
[LLVMdev] IR extension proposal: bitset constants
I would start from using module-level metadata.
An IR extension might be a good idea once we show that
- the proposed indirect call protection mechanism is efficient and
useful, and
- there are other use cases for the IR extension.
--kcc
On Wed, Jan 28, 2015 at 2:57 AM, Sean Silva <chisophugis at gmail.com> wrote:
> Is there any way to accomplish this that doesn't require
2015 Jan 30
0
[LLVMdev] IR extension proposal: bitset constants
Hi Peter,
Please forgive if this is an obvious question, but how reasonable is it for this approach to work when not all translation units are available to be rebuilt with the new information?
I'm very interested in what you're proposing here.
Jim
Sent from my iPhone
> On Jan 27, 2015, at 1:07 PM, Peter Collingbourne <peter at pcc.me.uk> wrote:
>
> Hi all,
>
> I
2016 Jan 28
8
Proposal: virtual constant propagation
Hi all,
I'd like to make the following proposal to implement an optimization called
virtual constant propagation.
==Introduction==
After enabling control flow integrity protection in Chromium, we have
observed an unacceptable performance regression in certain critical layout
microbenchmarks. Profiling [0] revealed that the cause of the regression was
a large number of virtual calls, each
2009 Dec 21
2
[LLVMdev] [PATCH] Implement dbgs()
On Monday 21 December 2009 10:14, Török Edwin wrote:
> On 2009-12-21 18:06, David Greene wrote:
> > On Saturday 19 December 2009 00:16, Chris Lattner wrote:
> >>> Or I think I can just assume (Yikes!) that if the signal handler is
> >>> invoked it will really be a circular_raw_ostream since the handler
> >>> should (!) only be set up in debug mode.
>
2015 Jan 31
2
[LLVMdev] IR extension proposal: bitset constants
On Sat, Jan 31, 2015 at 02:17:22PM -0800, JF Bastien wrote:
> On Sat, Jan 31, 2015 at 2:07 PM, Peter Collingbourne <peter at pcc.me.uk>
> wrote:
>
> > On Sat, Jan 31, 2015 at 11:35:01AM -0800, JF Bastien wrote:
> > > Trying to summarize all opinions expressed here: Peter is proposing an
> > > initial implementation that would only work with LTO. Folks seem
2015 Jan 31
0
[LLVMdev] IR extension proposal: bitset constants
On Sat, Jan 31, 2015 at 2:07 PM, Peter Collingbourne <peter at pcc.me.uk>
wrote:
> On Sat, Jan 31, 2015 at 11:35:01AM -0800, JF Bastien wrote:
> > Trying to summarize all opinions expressed here: Peter is proposing an
> > initial implementation that would only work with LTO. Folks seem put off
> by
> > this implementation affecting IR without having proven itself,
2015 Jan 31
2
[LLVMdev] IR extension proposal: bitset constants
On Sat, Jan 31, 2015 at 11:35:01AM -0800, JF Bastien wrote:
> Trying to summarize all opinions expressed here: Peter is proposing an
> initial implementation that would only work with LTO. Folks seem put off by
> this implementation affecting IR without having proven itself, and having
> shortcomings (as Jim pointed out). Kostya proposed going through metadata
> (and Chris kind of
2015 Jan 30
2
[LLVMdev] IR extension proposal: bitset constants
Hi Chris,
I wanted to start by giving an explanation of what I am trying to achieve
and how I am trying to achieve it.
I am working towards introducing into LLVM a security mechanism, Forward
Control Flow Integrity (CFI), that is designed to mitigate against
vulnerabilities that allow attacks based on corrupting vtable or function
pointers in memory in order to subvert a program's control
2015 Jan 27
7
[LLVMdev] IR extension proposal: bitset constants
Hi all,
I would like to propose a mechanism that allows IR modules to co-operatively
build a pointer set corresponding to addresses within a given set of
globals. The specific use case I have in mind is to provide a mechanism
for a C++ program to efficiently verify (at each call site) that a vtable
pointer is in the set of valid vtable pointers for the class or its derived
classes. One way of
2016 Jan 28
2
Proposal: virtual constant propagation
Hi,
I just thought about another use case: VTable compression.
If you know that an entry in the Vtable is never used, just remove it!
I’d hope we could even eliminate some unused virtual functions from the final binary.
—
Mehdi
> On Jan 27, 2016, at 10:29 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hi Peter,
>
> Pete (Cooper, CC'ed) had a
2011 Oct 07
1
BitSet equivalent? Java code usable?
Hi all,
I consider writing a R package on statistics for the sorting method as a hobby. I have written a private Java application that I could use as a basis. Therefore I'd like to ask two questions:
1) logical vectors: Bit storage (small) and capable of bit operations?
The Java application relies on BitSet(s) for efficiency reasons. Arrays of logical values cost far too much memory (in the
2019 Apr 04
2
[RFC] Proposed update to convert two 64-bit attribute bitmasks to std::bitset
There are two 64-bit bitmasks maintained in AttributeImpl.h<https://sdocc.itg.ti.com/ui#file:review=11893/version=393846>:
- AvailableFunctionAttrs is part of the AttributeListImpl class, and
- AvailableAttrs is part of the AttributeSetNode class
Both of these assume that the number of available enum attributes is limited to 64. In fact, a static_assert in
2013 Mar 22
0
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
On Thu, Mar 21, 2013 at 12:29 AM, Steven Su <steven_known at yahoo.com.cn> wrote:
> Hi, Daniel, thank you for your advice.
> Yes, ALL_MEMORY points to ALL_MEMORY.
>
> We use MD(memory descriptor) to abstract a memory location.
> MD contains 4 main fields: id, base, offset, size.
> For these special MD (ALL_MEMORY, GLOBAL_MEMORY, STACK_MEMORY, HEAP_MEMORY),
> we give them
2009 Dec 21
2
[LLVMdev] [PATCH] Implement dbgs()
On Saturday 19 December 2009 00:16, Chris Lattner wrote:
> > Or I think I can just assume (Yikes!) that if the signal handler is
> > invoked it will really be a circular_raw_ostream since the handler
> > should (!) only be set up in debug mode.
> >
> > That scares me a bit, though.
>
> Why don't you just check #ifndef NDEBUG like the code that sets it up?
2013 Mar 21
2
[LLVMdev] How to describe a pointer that points to All memory(include global memory, heap, stack)?
Hi, Daniel, thank you for your advice.
Yes, ALL_MEMORY points to ALL_MEMORY.
We use MD(memory descriptor) to abstract a memory location.
MD contains 4 main fields: id, base, offset, size.
For these special MD (ALL_MEMORY, GLOBAL_MEMORY, STACK_MEMORY, HEAP_MEMORY),
we give them id 1, 2, 3, 4, that means MD1 is ALL_MEMORY, MD2 is GLOBAL_MEMORY, the same goes for the rest.
Then we maintain a
2015 Jan 30
3
[LLVMdev] IR extension proposal: bitset constants
On Thu, Jan 29, 2015 at 02:22:48PM -0800, Peter Collingbourne wrote:
> I've been working on a patch that implements the bitset attribute and bitset
> lowering pass. I'll see if I can send it out later today.
http://reviews.llvm.org/D7288
Thanks,
--
Peter
2015 Jan 30
0
[LLVMdev] IR extension proposal: bitset constants
> On Jan 29, 2015, at 6:50 PM, Peter Collingbourne <peter at pcc.me.uk> wrote:
>
> On Thu, Jan 29, 2015 at 02:22:48PM -0800, Peter Collingbourne wrote:
>> I've been working on a patch that implements the bitset attribute and bitset
>> lowering pass. I'll see if I can send it out later today.
>
> http://reviews.llvm.org/D7288