similar to: [LLVMdev] How to handle size_t in front ends?

Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] How to handle size_t in front ends?"

2010 Jul 21
0
[LLVMdev] Casting.h illness
Is this a recommended approach/good style/good idea to use dyn_cast_or_null<X>(I) instead of dyn_cast_or_null<X>(*I)? (And other is and cast functions). Eugene On Wed, Jul 21, 2010 at 12:42 PM, Gabor Greif <gabor at mac.com> wrote: > Hi all, > > at the moment I am trying to fix an unnecessary iterator dereferencing > in Casting.h and am uncovering several ugly
2008 May 08
1
[LLVMdev] How to handle size_t in front ends?
On 2008-05-07, at 16:24, Chris Lattner wrote: > On Wed, 7 May 2008, Gordon Henriksen wrote: > >>> What would this be used for? How is it defined? How does >>> arithmetic work on it? >> >> Looking up the intptr type via TargetData is not a significant >> issue for me, but I can see the appeal, and how its absence could >> constitute a
2010 Jul 21
2
[LLVMdev] Casting.h illness
Hi all, at the moment I am trying to fix an unnecessary iterator dereferencing in Casting.h and am uncovering several ugly things. For example, look at this code: > // dyn_cast_or_null<X> - Functionally identical to dyn_cast, except that a null > // value is accepted. > // > template <class X, class Y> > inline typename cast_retty<X, Y>::ret_type
2012 Jul 14
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
Chandler Carruth wrote: > On Fri, Jul 13, 2012 at 1:40 PM, Benjamin Kramer <benny.kra at gmail.com > <mailto:benny.kra at gmail.com>> wrote: > > > On 13.07.2012, at 21:39, Gabor Greif <gabor.greif at alcatel-lucent.com > <mailto:gabor.greif at alcatel-lucent.com>> wrote: > > > Benjamin Kramer wrote: > >> On 13.07.2012,
2013 Aug 08
2
[LLVMdev] [Polly] Summary of some expensive compiler passes, especially PollyDependence
Hi all, I have summarized the top 10 compiler passes for Polly when compiling LLVM test-ssuite. Results can be viewed on: https://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 Based on the comparison between "clang -O3" and "polly -O3" listed on:
2008 May 07
0
[LLVMdev] How to handle size_t in front ends?
On Wed, 7 May 2008, Gordon Henriksen wrote: >> What would this be used for? How is it defined? How does >> arithmetic work on it? > > Looking up the intptr type via TargetData is not a significant issue > for me, but I can see the appeal, and how its absence could constitute > a significant barrier to generating portable IR (provided, of course, > a portable language).
2017 May 06
2
Build polly-amd64-linux Failure
On Sat, May 6, 2017, at 04:28 PM, llvm.buildmaster at lab.llvm.org wrote: > The Buildbot has detected a failed build on builder polly-amd64-linux > while building polly. > Full details are available at: > http://lab.llvm.org:8011/builders/polly-amd64-linux/builds/6539 > > Buildbot URL: http://lab.llvm.org:8011/ > > Buildslave for this Build: grosser1 > > Build
2013 Aug 08
0
[LLVMdev] [Polly] Summary of some expensive compiler passes, especially PollyDependence
On 08/08/2013 01:29 AM, Star Tan wrote: > Hi all, > > > I have summarized the top 10 compiler passes for Polly when compiling LLVM test-ssuite. Results can be viewed on: > https://gist.github.com/tanstar/581bcea1e4e03498f935/raw/f6a4ec4e8565f7a7bbdb924cd59fcf145caac039/Polly-top10 > > > Based on the comparison between "clang -O3" and "polly -O3"
2012 Jul 13
2
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
On Fri, Jul 13, 2012 at 1:40 PM, Benjamin Kramer <benny.kra at gmail.com>wrote: > > On 13.07.2012, at 21:39, Gabor Greif <gabor.greif at alcatel-lucent.com> > wrote: > > > Benjamin Kramer wrote: > >> On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> > wrote: > >> > >>> Hi all, > >>> >
2008 May 07
0
[LLVMdev] How to handle size_t in front ends?
On May 6, 2008, at 11:49 PM, Jonathan S. Shapiro wrote: > On Tue, 2008-05-06 at 23:18 -0700, Chris Lattner wrote: >>> 1) Is there a way to declare an integer type in the IR that >>> represents >>> "an int the same size as a pointer" without specifying exactly the >>> size >>> of a pointer? >> >> No. > > Chris: > >
2010 Jul 21
2
[LLVMdev] Casting.h illness
On Jul 21, 2010, at 12:49 PM, Eugene Toder wrote: > Is this a recommended approach/good style/good idea to use > dyn_cast_or_null<X>(I) instead of dyn_cast_or_null<X>(*I)? (And other > is and cast functions). We generally don't want auto-dereference. There is some special magic for unwrapping Uses etc though. Is this what you're in contact with Gabor? -Chris >
2012 Jul 13
2
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
Benjamin Kramer wrote: > On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> wrote: > >> Hi all, >> >> I am in charge of the controlled introduction of clang into >> our builds at my workplace. Since all our tools must run from >> a ClearCase view for automatic dependency tracking, we have been >> biten by a Linux bug, and
2008 May 07
3
[LLVMdev] How to handle size_t in front ends?
On Tue, 2008-05-06 at 23:18 -0700, Chris Lattner wrote: > > 1) Is there a way to declare an integer type in the IR that represents > > "an int the same size as a pointer" without specifying exactly the > > size > > of a pointer? > > No. Chris: There are other languages that specify a "word" type along these lines. Would it be worth considering
2012 Jul 13
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
On 13.07.2012, at 21:39, Gabor Greif <gabor.greif at alcatel-lucent.com> wrote: > Benjamin Kramer wrote: >> On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> wrote: >> >>> Hi all, >>> >>> I am in charge of the controlled introduction of clang into >>> our builds at my workplace. Since all our tools must run
2012 Jul 13
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
On 13.07.2012, at 09:46, Gabor Greif <gabor.greif at alcatel-lucent.com> wrote: > Hi all, > > I am in charge of the controlled introduction of clang into > our builds at my workplace. Since all our tools must run from > a ClearCase view for automatic dependency tracking, we have been > biten by a Linux bug, and readlink("/proc/self/exe", ...) gives >
2008 May 07
5
[LLVMdev] How to handle size_t in front ends?
On 2008-05-07, at 03:05, Chris Lattner wrote: > On May 6, 2008, at 11:49 PM, Jonathan S. Shapiro wrote: > >> There are other languages that specify a "word" type along these >> lines. Would it be worth considering adding such a type to the IR, >> or is there a reason not to do so that I am failing to see? > > What would this be used for? How is it
2013 Dec 04
2
[LLVMdev] Empty files ending up installed
Hello all! I have found following empty files that get installed (v3.4rc2) : docs/llvm/html/Dummy.html include/clang/Driver/CC1Options.h What is the story behind them? Or were they just forgotten? Can we (someone) remove these? Cheers, Gabor
2008 May 07
2
[LLVMdev] How to handle size_t in front ends?
On Wed, 2008-05-07 at 14:25 -0700, Chris Lattner wrote: > On Wed, 7 May 2008, Jonathan S. Shapiro wrote: > > >> On Wed, 2008-05-07 at 13:24 -0700, Chris Lattner wrote: > >> Querying TargetData only works if you know the size of the pointer. :) > > > In the end, the use case that concerns me is things like character > > vectors, because of the fact that the
2008 May 07
0
[LLVMdev] How to handle size_t in front ends?
On Wed, 7 May 2008, Jonathan S. Shapiro wrote: >> >> i64 should be big enough for this. Just use i64. > > On a 32-bit platform, doesn't one want to use i32? Why? What is wrong with i64? -Chris -- http://nondot.org/sabre/ http://llvm.org/
2008 May 08
0
[LLVMdev] How to handle size_t in front ends?
On Wed, 7 May 2008, Jonathan S. Shapiro wrote: > On Wed, 2008-05-07 at 16:09 -0700, Chris Lattner wrote: >> On Wed, 7 May 2008, Jonathan S. Shapiro wrote: >>>> >>>> i64 should be big enough for this. Just use i64. >>> >>> On a 32-bit platform, doesn't one want to use i32? >> >> Why? What is wrong with i64? > > On its face,