Displaying 20 results from an estimated 4000 matches similar to: "Question about GCC warnings"
2018 Sep 13
2
New warnings when building trunk with GCC 9
Hello,
GCC 9.0 introduces a new warning checkers and some of them found possible
issues in LLVM.
In file included from
/home/davidbolvansky/trunk/llvm/include/llvm/Analysis/LazyCallGraph.h:38,
from
/home/davidbolvansky/trunk/llvm/unittests/Analysis/LazyCallGraphTest.cpp:10:
/home/davidbolvansky/trunk/llvm/include/llvm/ADT/ArrayRef.h: In
instantiation of
2016 Aug 24
2
Pointer to temporary issue in ArrayRefTest.InitializerList
Hi all-
I am mostly doing work in Clang (and am new there), so I apologize if this isn't the proper place to mention this. I appreciate guidance in advance.
I was looking into some of the unit tests, and noticed that the ArrayRefTest.InitializerList, and thus the InitializerList constructor of ArrayRef (under normal use-case) hit undefined behavior. The test does the following:
2016 Aug 24
2
Pointer to temporary issue in ArrayRefTest.InitializerList
Sorry for the inline-comment format being weird, I haven't figured out yet how to do '>' stuff in outlook yet :/ Hopefully this is clear enough.
-----Original Message-----
From: mehdi.amini at apple.com [mailto:mehdi.amini at apple.com]
Sent: Wednesday, August 24, 2016 10:55 AM
To: Keane, Erich <erich.keane at intel.com>
Cc: llvm-dev at lists.llvm.org
Subject: Re:
2019 Apr 11
2
128 bit float constant
Hi Tim,
Thanks for the hint.
I tried the following, (it's a C interface since that's what I need it for)
where a and b are
the top and bottom halves of the 128 bit value,
LLVMValueRef TestConst(LLVMContextRef C, uint64_t a, uint64_t b) {
Type *ty = Type::getFP128Ty(*unwrap(C));
ArrayRef<uint64_t> ar[2] = {a,b};
APInt ai(128,*ar);
APFloat quad(APFloat::IEEEquad(), ai);
2020 Apr 30
2
Discrepancy between Debug and Release+Asserts versions of Clang/LLVM
I agree that the ArrayRef is likely the issue. I've debugged a crash caused
by a temporary ArrayRef like that a couple times.
Either do what David suggested or use a normal array:
Metadata *mdArray[] = {ConstantInt::get(Int64Ty, 0), newMD};
~Craig
On Thu, Apr 30, 2020 at 9:56 AM David Blaikie via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
>
> On Thu, Apr 30, 2020 at
2006 May 17
8
Html Email Problem
Dear Rubyians,
I am facing problems to send Html Email scnce one month.
I changed the content type is text/html and charecter set "utf-8"
I worte the html code in the confirm.heml in the action mailer folder.
but mail is going with html code
Exapmle: <html border="2"> <tr><td></td></tr></html> code in the
confirm .html
In the
2003 Nov 05
1
read.table leaves out data when reading multiple-line records (PR#4955)
Dear all,
I discovered that read.table (RW1.8.0) leaves out data when reading
multiple-line records.
Replication code at the end
Best regards
Jens Oehlschlägel
> filename <- "c:/tmp/c2.csv"
>
> data <- data.frame(a=c("c", "e\nnewline"), b=c("d", '"quoted
simpleline"'))
>
> #look at the data
>
2016 Jun 20
2
Compilation problem with a few configure option
Hi
Compilation of 1.3.7 dies with the following configuration:
====================================
./configure --enable-shared --enable-static --disable-sse
--disable-backend-inmemory --disable-backend-remote
====================================
During the compilation I get the following error:
====================================
/bin/bash ./libtool --tag=CXX --mode=link g++ -fshow-column
2008 Jun 11
1
read.table() causes segfault with incorrect data (PR#11627)
Full_Name: Juho Vuori
Version: 2.7.0 (2008-04-22)
OS: Linux poseidon.fimr.fi 2.6.23.17-88.fc7PAE #1 SMP Thu May 15 00:22:53 EDT 2008 i686 i686 i386 GNU/Linux
Submission from: (NULL) (193.166.188.194)
Calling read.table() twice the following way causes a segmentation fault in R.
Run R and type the following commands:
> read.table(stdin())
0: 1 2 3
1: 3
2:
Error in scan(file, what, nmax, sep,
2009 Sep 12
3
[LLVMdev] [proposal] Extensible IR metadata
Dan Gohman wrote:
> On Sep 11, 2009, at 9:57 AM, Chris Lattner wrote:
>
>
>> Devang's work on debug info prompted this, thoughts welcome:
>> http://nondot.org/sabre/LLVMNotes/ExtensibleMetadata.txt
>
> The document mentions "instructions" a lot. We'll want to be able to
> apply metadata to ConstantExprs as well at least, if not also Arguments
>
2014 Jul 18
2
[LLVMdev] Bug in llvm/ADT/ArrayRef.h?
Hi,
I think I ran into a rather subtle bug inside llvm/ADT/ArrayRef.h which
only shows up when compiling the code with GCC-4.8 with switched-off
optimizations. (Both clang and GCC-4.7 don't trigger the bug.)
I already filed a bug against GCC-4.8 which was rejected by the GCC-folks
as being invalid, because the code (basically ArrayRef.h) "is doing
something bad - it's retaining a
2014 Aug 22
2
[LLVMdev] Addressing const reference in ArrayRef
On Fri, Aug 22, 2014 at 11:22 AM, Duncan P. N. Exon Smith
<dexonsmith at apple.com> wrote:
>
>> On 2014-Aug-22, at 10:43, David Blaikie <dblaikie at gmail.com> wrote:
>>
>> Yep - the convenience of one-element->ArrayRef is "cute" at best, I
>> think. Having to wrap it doesn't seem detrimental. Would have to look
>> at some numbers,
2014 Aug 22
4
[LLVMdev] Addressing const reference in ArrayRef
On Fri, Aug 22, 2014 at 10:16 AM, Duncan P. N. Exon Smith
<dexonsmith at apple.com> wrote:
>> On 2014-Aug-21, at 10:39, David Blaikie <dblaikie at gmail.com> wrote:
>>
>> On Thu, Aug 21, 2014 at 10:34 AM, Reid Kleckner <rnk at google.com> wrote:
>>> Is there some way we can get lifetime extension of temporaries to kick in
>>> here?
>>
2009 Oct 20
5
ssh user equivalence
We are getting some pushback from our SA group regarding root having ssh
user equivalence on the cluster where we run OCFS2.
Is it required to have the ssh user equivalence setup for the root user
when running OCFS2 ?
Thanks in advance,
Reid
Reid McKinley
********************************************************************************************
This message, including any
2014 Aug 20
3
[LLVMdev] Addressing const reference in ArrayRef
Analyzing why GCC failed to build LLVM recently, one root cause lies
in definition of ArrayRef:
// ArrayRef.h:
ArrayRef(const T &OneElt) : Data(&OneElt), Length(1) {}
Here address of const reference is taken and stored to an object. It
is believed that live range of const reference is only at the function
call site, escaping of its address to an object with a longer live
range is invalid.
2014 Aug 21
2
[LLVMdev] Addressing const reference in ArrayRef
On Thu, Aug 21, 2014 at 10:34 AM, Reid Kleckner <rnk at google.com> wrote:
> Is there some way we can get lifetime extension of temporaries to kick in
> here?
Nope - since the temporary is a subexpression - not the thing being declared.
>
>
> On Thu, Aug 21, 2014 at 8:05 AM, David Blaikie <dblaikie at gmail.com> wrote:
>>
>> Yeah - I suspect there are just
2018 May 26
2
Buffering in R 3.5 connections causes incorrect data in readChar
I noticed an issue where readChar does not return the correct value after a
call to readline. It appears that readChar is not aware of the buffering,
so it reads from the end of the buffer, rather than the current position in
the file. This is a significant change of behavior from R-3.4.4.
Below is a test case that I used to home in on the problem.
---
p<-"test2.txt"
2019 May 03
3
ArrayRef vs SmallVectorImpl
It is suggested in the documentation that if you would have declared a
function parameter as SmallVector<Foo,N>&, it is better to instead declare
it as SmallVectorImpl<Foo>&.
This makes sense, but it seems to me that it is better still to declare it
as ArrayRef<Foo>; a quick test suggests it compiles to the same (highly
efficient) code, and adds a bit more flexibility in
2012 Jan 22
2
[LLVMdev] CreateGlobalStringPtr giving linker errors
Hi,
I am trying to use some LLVM API in my C++ code, and I end up getting
linker errors. I am working on Apple MacOSX Lion. Using g++ for the
compile. It is the CreateGlobalStringPtr which is throwing the error. This
is LLVM 3.0.
Here's the codeI am trying to use some LLVM API in my C++ code, and I end
up getting linker errors. I am working on Apple MacOSX Lion. Using g++ for
the compile. It
2018 May 29
1
Buffering in R 3.5 connections causes incorrect data in readChar
Tomas,
Thank you for the explanation. I see in the documentation: "These functions
are intended to be used with binary-mode connections." So I see how using
it on a text connection is undefined, and not a bug. An error or warning
when attempting to use a it on a text connection would be helpful
considering how the behavior has changed in R-3.5.
On Tue, May 29, 2018 at 3:09 AM, Tomas