similar to: [LLVMdev] Is this a bug in clang?

Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] Is this a bug in clang?"

2011 Apr 20
3
[LLVMdev] Is this a bug in clang?
This code is undefined, meaning that all bets are off, don't do it. I.e. It reads the value of I between two sequence points and uses it for something other than determining the value written. From: Csaba Raduly Sent: Tuesday, April 19, 2011 3:44 AM To: Joe Armstrong Cc: llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] Is this a bug in clang? Hi Joe On Tue, Apr 19, 2011 at 10:59 AM, Joe
2011 Apr 20
0
[LLVMdev] Is this a bug in clang?
So... Are 40 and 41 the only legal behaviors or are there more? Robby On Tuesday, April 19, 2011, Ahmed Charles <ahmedcharles at gmail.com> wrote: > This code is undefined, meaning that all bets are off, don't do it. > I.e. It reads the value of I between two sequence points and uses it > for something other than determining the value written. From: Csaba > Raduly >
2001 Aug 02
1
arrows()/log scale/clipping (?) (PR#1039)
arrows() seems to hang when either x or y scale of the plot is logarithmic and the arrows requested go beyond the plot (by more than a certain amount). I didn't go into C code to find it, but here's a function that exercises the bug a bit ... arrow.bug2 <- function(y0=1,y1=10,log="y") { plot(c(0.1,1),c(1,10),log=log) arrows(x0=0.5, y0=y0, x1=0.5,
2011 Apr 27
3
[LLVMdev] confused about float literals
On Wed, Apr 27, 2011 at 12:51 AM, John McCall <rjmccall at apple.com> wrote: > On Apr 26, 2011, at 2:07 AM, Joe Armstrong wrote: >> Compiles (via clang) to: >> >>  ; ModuleID = 'test101.c' >>  target datalayout = >>
2011 Apr 20
2
[LLVMdev] Is this a bug in clang?
On Wed, Apr 20, 2011 at 10:44 AM, Joe Armstrong wrote: > > It seems very strange to me that the ansi standard says "XXX is > undefined" and that both clang and gcc > can detect that something is undefined and that by default they > compile the offending code without > any feelings of guilt. "The good thing — the only good thing! — about undefined behavior in
2007 Jun 28
4
Sweave bug? when writing figures / deleting variable in chunk
I have found a quite strange (to me) behaviour in Sweave. It only occurs in the following situation: 1. define a variable in one chunk 2. use it within a subsequent figure-generating chunk 3. delete it at the end of that same chunk Then the Sweave driver chokes, not finding the variable name when generating the figure Example: % document bug2.Rnw \documentclass{article} \usepackage{Sweave}
2011 Apr 26
0
[LLVMdev] confused about float literals
On Apr 26, 2011, at 2:07 AM, Joe Armstrong wrote: > Compiles (via clang) to: > > ; ModuleID = 'test101.c' > target datalayout = > "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32" > target triple = "i386-pc-linux-gnu" > > define i32 @main() nounwind { > %1 =
2011 Apr 26
2
[LLVMdev] confused about float literals
I assumed that C floats are 32 bits and doubles 64 bits ... but This code int main(){ float f; double f1; f = 3.145; f1 = 3.145; return(0); } Compiles (via clang) to: ; ModuleID = 'test101.c' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32" target triple =
2011 Apr 20
5
[LLVMdev] Is this a bug in clang?
> So... Are 40 and 41 the only legal behaviors or are there more? Since the program invokes undefined behavior, anything goes. The compiler is perfectly within its rights to send a rude email to your department chair if you compile that code. John
2011 Apr 20
0
[LLVMdev] Is this a bug in clang?
On Wed, Apr 20, 2011 at 7:50 AM, John Regehr <regehr at cs.utah.edu> wrote: >> So... Are 40 and 41 the only legal behaviors or are there more? > > Since the program invokes undefined behavior, anything goes. > > The compiler is perfectly within its rights to send a rude email to your > department chair if you compile that code. > > John > Ummmm The problem is
2011 Mar 16
5
[LLVMdev] Bug in opt
I have a problem. I'm writing a C compiler in my favorite programming language (don't ask :-) I have made a .s file, which can be correctly assembled and run with lli. But when I optimize it I get no errors from the optimizer, but the resultant file is incorrect. Here's what happens: llvm-as test2_gen.s %% no errors test2_gen.s.bc is produced lli test2_gen.s.bc n=887459712
2008 Apr 25
2
Bug in R 2.7 for over long lines (crasher+proposed fix!) (PR#11281)
OK, I am just sending it here too as it looks like r-devel at r-project.org is not the right place: =EF=BB=BFOn Fri, 2008-04-25 at 08:48 +0200, Soeren Sonnenburg wrote: > While trying to fix swig & R2.7 I actually discovered that there is a > bug in R 2.7 causing a crash (so R & swig might actually work): >=20 > the bug is in ./src/main/gram.c line 3038: >=20 >
2011 May 13
3
[LLVMdev] IO intrinsics?
I found these lines in the BrainF example: //declare i32 @getchar() getchar_func = cast<Function>(module-> getOrInsertFunction("getchar", IntegerType::getInt32Ty(C), NULL)); //declare i32 @putchar(i32) putchar_func = cast<Function>(module-> getOrInsertFunction("putchar", IntegerType::getInt32Ty(C),
2005 Mar 14
4
[SMB 3.0.10] File Locking Mechanism Windows <-> Unix
Hello, Iam facing a problem in locking of files across samba shares. We have samba 3.0.10 running on Solaris 9 with the smb.conf as follows. # Global parameters [global] workgroup = NMUINT netbios name = NMUINTFS interfaces = <IP> bind interfaces only = Yes security = DOMAIN password server = XXX.XXX.XXX.XXX log level = 1 ldap
2013 Jul 22
4
[PATCH V3 0/2] [BUGFIX] virtio/console: Fix two bugs of splice_write
Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each
2013 Jul 22
4
[PATCH V3 0/2] [BUGFIX] virtio/console: Fix two bugs of splice_write
Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each
2007 Apr 18
7
[Bridge] (no subject)
Dear Sir, I was trying to install bridge as we are installing scps gateway in our testbed.This requires us to install the bridge. Our Linux version is 2.4.18 ~3 and we are using redhat 7.2 Please let me know which is the bridge I should install and how to configure it. Before configuring the bridge what I should check in my configuration. Thanks for your time, Sincerely Rama ===== I hear
2011 Jan 04
0
R CMD check bug or misfeature
This is a bug/misfeature report for R CMD check. The function tools:::.check_packages_used_in_tests Gives an apparently unintended error when checking the tests in the contributed package rcdd_1.1-3.tar.gz as found on CRAN. See the script below for details. The actual error reported is totally mysterious. * checking for unstated dependencies in tests ... NOTE Error in
2009 Mar 04
5
[PATCH 0/2] ocfs2: two bug fixes about xattr and inline-data
Mark and Joel, I found two serious bugs about xattr and inline-data. the first bug: in ocfs2_mknod(), we check and found the ACL or security xattr entry could be set into inode in ocfs2_calc_xattr_init(), then don't reserve block for them. But in ocfs2_mknod_locked(), if we found ocfs2 support inline-data, then set id_count with the max_inline_data. After that, we set acl/security xattr
2011 Apr 20
0
[LLVMdev] Is this a bug in clang?
On Wed, Apr 20, 2011 at 11:24 AM, Csaba Raduly <rcsaba at gmail.com> wrote: > On Wed, Apr 20, 2011 at 10:44 AM, Joe Armstrong  wrote: >> >> It seems very strange to me that the ansi standard says "XXX is >> undefined" and that both clang and gcc >> can detect that something is undefined and that by default they >> compile the offending code without