Displaying 3 results from an estimated 3 matches for "trollchris".
2013 Dec 10
2
[LLVMdev] lit: deprecating trailing \ in RUN lines
...sed the trailing space. That makes it a bit odd, to say the least. If we have any files with that construct in it, we should totally just run a regex over them to fix it. That’s just broken.
This would also totally have been prevented if we had a post-commit hook to strip trailing whitespace. </trollchris>
2013 Dec 10
0
[LLVMdev] lit: deprecating trailing \ in RUN lines
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Alp Toker
> Subject: Re: [LLVMdev] lit: deprecating trailing \ in RUN lines
> //\
> int x=0;
> int x=0;
> $ gcc-4.9 -fsyntax-only f.c
Try gcc with -Wall, and you'll see the appropriate warning. Also try the MS compiler after removing the trailing space after the backslash; I
2013 Dec 10
4
[LLVMdev] lit: deprecating trailing \ in RUN lines
On 10/12/2013 19:47, Jim Grosbach wrote:
>
> On Dec 10, 2013, at 11:26 AM, Alp Toker <alp at nuanti.com
> <mailto:alp at nuanti.com>> wrote:
>
>>
>> On 10/12/2013 18:03, Jim Grosbach wrote:
>>>> That causes dissonance between what the compiler sees and what
>>>> lit.py sees for no particularly good reason. One of the nice