Displaying 17 results from an estimated 17 matches for "bevin".
Did you mean:
begin
2020 Jun 24
2
Target specific named address spaces
Hi,
Is there a way to implement named address spaces with clang/llvm as it is
possible with gcc ?
We would like to have our own named address space that would be recognized
by the frontend.
Thanks in advance!
Regards,
Sebastien
2020 Jul 08
4
[RFC] Saturating left shift intrinsics
....html
It is of course possible to emit these shifts as regular IR instructions, but targets which support saturating shifts might have difficulties efficiently selecting native instructions if the optimizer undoes the particular expected instruction pattern that the shifts would be selected on.
/ Bevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200708/1c67fe84/attachment.html>
2019 May 29
2
Problem of getNumOperands() for CallInst
Hi all,
I got a interesting problem when calling getNumOperands() of CallInst.
For example,
call void @_Z2f2PA100_i([100 x i32]* nonnull %arraydecay)
If I use getNumOperands(), it will return 2.
However, if I use getCalledFunction()->getNumParams(), it will return 1.
According to the IR, I think the number of operands of the call instruction should be 1.
I
2018 Jun 12
2
ModulePass cannot be registered as EarlyAsPossible
Hello all,
I've followed the example in
https://github.com/CompilerTeaching/SimplePass/blob/master/SimplePass.cc in
order to create a custom pass.
The pass needs to be added before any transformation, so I used
EP_EarlyAsPossible extension point to register it. Furthermore, I need to
access to every GlobalVariable in the IR, so my pass has to be a
ModulePass, like this:
struct MyPass :
2015 Apr 28
2
[LLVMdev] RFC: Machine Level IR text-based serialization format
...er
to diff and read.
There are parts of the suggested YAML format that seem to require some
parsing anyway, like the instruction strings. If YAML is going to be
used,
I think it would be better to let the instructions be encoded in YAML
instead of leaving them as a string, if that makes sense.
/ Bevin
2018 Aug 23
4
[DebugInfo] DIBuilder missing interface to generate DWARF info for packed_decimal basic type.
Hello Paul,
Thanks for the reply.
Yes, I am only looking for dwarf support at the moment and planning to support both PLI/COBOL decimal types. Also thanks for the suggestion, you are right as it is going to be rare cases, so it will be better to implement a separate subclass to avoid memory overhead for others.
>> (Somebody is actively working on scaled binary operations, although they
2015 Apr 28
2
[LLVMdev] RFC: Machine Level IR text-based serialization format
...hich could be filled in by sensible defaults: the function "number", the basic block number, predecessors and successors of a basic block, maybe allowing to leave out the llvm IR (though that probably is not allowed by CodeGen at the moment).
- Matthias
> On Apr 28, 2015, at 2:08 PM, Bevin Hansson <bevinh at sics.se> wrote:
>
> On 2015-04-28 20:18, Alex L wrote:
>> 2015-04-28 10:15 GMT-07:00 Hal Finkel <hfinkel at anl.gov>:
>> Hi Alex,
>> I think this looks promising. What are the 1 an 4 above? How are you
>> proposing to serialize operand f...
2015 Apr 28
2
[LLVMdev] RFC: Machine Level IR text-based serialization format
2015-04-28 10:15 GMT-07:00 Hal Finkel <hfinkel at anl.gov>:
>
> ------------------------------
>
> *From: *"Alex L" <arphaman at gmail.com>
> *To: *"LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
> *Sent: *Tuesday, April 28, 2015 11:56:42 AM
> *Subject: *[LLVMdev] RFC: Machine Level IR text-based serialization format
>
>
2018 Aug 20
7
Fixed Point Support in LLVM
...s would be added for these operations:
- signed multiplication
- signed saturating multiplication
- signed division
- unsigned division
- signed saturating division
- unsigned saturating division
- saturation
- saturating addition
- saturating subtraction
- floating-point to fixed-point conversion
Bevin Hansson has implemented these in his downstream version of
clang/llvm (http://lists.llvm.org/pipermail/cfe-dev/2018-May/058019.html),
and I imagine this is all we may need for intrinsics. We would like to
offset complicated instructions to llvm for targets that provide
native support for these oper...
2018 Aug 22
2
Fixed Point Support in LLVM
...ions in textual IR, but this doesn't help
when you're printing.
> - Targets that want to pass fixed-point values differently from integers have to
> invent some extra way of specifying that a value is fixed-point.
Another function attribute would probably be fine for that.
/ Bevin
2019 Jul 04
3
RFC: Complex in LLVM
> On Jul 3, 2019, at 4:43 PM, Krzysztof Parzyszek via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> -----Original Message-----
> From: David Greene <dag at cray.com>
> Sent: Wednesday, July 3, 2019 2:44 PM
> To: Krzysztof Parzyszek via llvm-dev <llvm-dev at lists.llvm.org>
> Cc: Krzysztof Parzyszek <kparzysz at quicinc.com>
> Subject: [EXT] Re:
2018 Aug 22
2
Fixed Point Support in LLVM
On 2018-08-22 11:32, John McCall wrote:
>
>> On Aug 22, 2018, at 4:38 AM, Bevin Hansson <bevin.hansson at ericsson.com> wrote:
>>
>>
>>
>> On 2018-08-22 05:56, John McCall via llvm-dev wrote:
>>>> On Aug 21, 2018, at 6:20 PM, Leonard Chan <leonardchan at google.com> wrote:
>>>> If we were to create a new type down the...
2018 Aug 21
4
Fixed Point Support in LLVM
...gt; > - signed division
> > - unsigned division
> > - signed saturating division
> > - unsigned saturating division
> > - saturation
> > - saturating addition
> > - saturating subtraction
> > - floating-point to fixed-point conversion
> >
> > Bevin Hansson has implemented these in his downstream version of
> > clang/llvm (http://lists.llvm.org/pipermail/cfe-dev/2018-May/058019.html),
> > and I imagine this is all we may need for intrinsics. We would like to
> > offset complicated instructions to llvm for targets that provide...
2006 Mar 15
0
wbinfo -u responds with Error looking up domain users
...4:System User:/home/njcloud:/bin/bash
acrardi:x:1035:513:System User:/home/acrardi:/bin/bash
kkkiefe:x:1036:513:System User:/home/kkkiefe:/bin/bash
tgmarcu:x:1037:513:System User:/home/tgmarcu:/bin/bash
kakeese:x:1041:1011:System User:/home/kakeese:/bin/bash
<snip>Hendricks users:
HENDRICKS\acbevin:*:150009:150000:Bevins, Armand
C.:/home/HENDRICKS/acbevin:/bin/false
HENDRICKS\acdusa:*:150010:150000:Dusa, Adrian
C:/home/HENDRICKS/acdusa:/bin/false
HENDRICKS\achagga:*:150011:150000:Haggard, Adalyn
C.:/home/HENDRICKS/achagga:/bin/false
HENDRICKS\achatt:*:150012:150000:Chattin,
Apastra:/home/HEND...
2019 Mar 02
3
Legalising seems to lose critical information needed for lowering return values properly?
I'm a new LLVM developer contributing patches for the AVR platform and I'm trying to understand which parts of the code base are malfunctioning in my case.
This LLVM IR...
define hidden i32 @setServoAngle3(i32) local_unnamed_addr {
entry:
%1 = call i32 @myExternalFunction1(i32 %0, i32 119)
ret i32 %1
}
declare i32 @myExternalFunction1(i32, i32)
Is being lowered to this assembly
2005 Mar 09
9
Unit testing + instance variables
After *much* digging and playing around, I finally figured out how to
unit test instance variables that are created by actions. It was
more difficult than I expected. It seems like there should have been
a more straight forward way to do this. Can someone enlighten me? A
simplified and somewhat contrived example of what I am current doing:
Thanks.
Matt
>>
# My Controller of interest
2015 Apr 28
9
[LLVMdev] RFC: Machine Level IR text-based serialization format
Hi all,
I would like to propose a text-based, human readable format that will be used to
serialize the machine level IR. The major goal of this format is to allow LLVM
to save the machine level IR after any code generation pass and then to load
it again and continue running passes on the machine level IR. The
primary use case
of this format is to enable easier testing process for the code