similar to: [LLVMdev] initialization list with conversion operator dont work properly and report error

Displaying 20 results from an estimated 6000 matches similar to: "[LLVMdev] initialization list with conversion operator dont work properly and report error"

2013 Sep 25
2
[LLVMdev] initialization list with conversion operator dont work properly and report error
Actually it should have not thrown error at all. it works fine with gcc. And the part of code which you mentioned is not getting hit at all. Maybe some difference in parsing is there. On Wed, Sep 25, 2013 at 5:29 AM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Mon, Sep 23, 2013 at 11:43 PM, Mayur Pandey <mayurthebond at gmail.com>wrote: > >> for the following
2013 Sep 24
0
[LLVMdev] initialization list with conversion operator dont work properly and report error
On Mon, Sep 23, 2013 at 11:43 PM, Mayur Pandey <mayurthebond at gmail.com>wrote: > for the following code: > > struct X > { > X(); > }; > > struct Y > { > operator X() const; > }; > > X a = { Y() }; // reports error: no matching constructor for > initialization of 'X' > X aa = Y(); // works fine > > > clang when compiled
2013 Sep 25
0
[LLVMdev] initialization list with conversion operator dont work properly and report error
I'm not really an overload resolution expert, so I could be wrong. Anyway, please file a bug report (http://llvm.org/bugs/), and our overload resolution experts will take a look. :) -Eli On Wed, Sep 25, 2013 at 6:34 AM, Mayur Pandey <mayurthebond at gmail.com>wrote: > Actually it should have not thrown error at all. it works fine with gcc. > And the part of code which you
2012 Dec 01
2
[LLVMdev] operator overloading fails while debugging with gdb for i386
Hi, Structures are passed by pointer, so the return value is not actually in eax. That code gets transformed into something like: void sum(A1 *out, const A1 one, const A1 two) { out->x = one.x + two.x out->y = one.y + two.y } So actually the function ends up returning void and operating on a hidden parameter, so %eax is dead at the end of the function and should not be being relied
2014 Nov 24
3
[LLVMdev] bx instruction getting generated in arm assembly for O1
Hi Mayur, > On 24 Nov 2014, at 07:00, MAYUR PANDEY <mayur.p at samsung.com> wrote: > In the assembly generated with O0, we are getting the "blx" instruction whereas with O1 we get "bx" (in 3.4.2 we used to get "blx" for both O0 and O1). > > Is this because of this patch: [llvm] r214959 - ARM: do not generate BLX instructions on Cortex-M CPUs
2012 Nov 29
2
[LLVMdev] operator overloading fails while debugging with gdb for i386
For the given test: class A1 { int x; int y; public: A1(int a, int b) { x=a; y=b; } A1 operator+(const A1&); }; A1 A1::operator+(const A1& second) { A1 sum(0,0); sum.x = x + second.x; sum.y = y + second.y; return (sum); } int main (void) { A1 one(2,3); A1 two(4,5); return 0; } when the exectable of this code is debugged in gdb for i386, we dont get the
2012 Dec 01
0
[LLVMdev] operator overloading fails while debugging with gdb for i386
Problem seems not only with operator overloading, It occurs with struct value returning also. gdb while debugging expects the return value in eax, gcc does returns in eax, But Clang returns in edx(it can be checked in gdb by printing the contents of edx). Code(sample code) struct A1 { int x; int y; }; A1 sum(const A1 one, const A1 two) { A1 plus = {0,0}; plus.x = one.x + two.x; plus.y
2012 Dec 03
1
[LLVMdev] operator overloading fails while debugging with gdb for i386
On 3 December 2012 10:42, Mayur Pandey <mayurthebond at gmail.com> wrote: > So this seems to be the cause of the problem. I guess you're mixing two different problems. First, is the possible lack of conformance with the ABI you state, which I can't comment since I don't know that ABI very well. Second, is the fact that clang is not printing correct debug information (or is
2012 Dec 02
0
[LLVMdev] operator overloading fails while debugging with gdb for i386
Hi, As you told that function ends up returning void, I just confirmed it in the IR, the function is defined as: define *void* @_Z3sum2A1S_(*%struct.A1* noalias sret %agg.result*, %struct.A1* byval align 4 %one, %struct.A1* byval align 4 %two). But when i checked the register values in g++, eax contains an address of stack, which points to the value (object) returned by sum. That is if we
2012 Dec 03
2
[LLVMdev] operator overloading fails while debugging with gdb for i386
On 2 December 2012 08:12, Mayur Pandey <mayurthebond at gmail.com> wrote: > So is this just a coincidence for g++ that eax points to this address and > gdb prints the right value on the command print sum(one,two)?? The code is small, and the structure is probably set at the end of the block, so I think it's not that much of a coincidence. Regardless of the specific value on that
2012 Dec 03
0
[LLVMdev] operator overloading fails while debugging with gdb for i386
Hi, I was going through this issue along with the standards. What the standard states is(reference: http://www.sco.com/developers/devspecs/abi386-4.pdf): If a function returns a structure or union, then the caller provides space for the return value and places its address on the stack as argument word zero. In effect, this address becomes a ‘‘hidden’’ first argument. Having the caller supply the
2011 Apr 12
2
advisory file locks in linux - do they work?
Hi - I'm trying to verify if OpenSSH/SFTP will in fact lock files with advisory file locking in Linux. I can test locking with the linux "flock" command to verify that file locking does work - but when I upload or download a file with SFTP it will not detect a lock. I'm asking about Linux specifically because about a year ago I was doing a similar process in Solaris 9 and
2020 Jan 15
4
[semi-OT] C7 Possible bug but I can't determine what tool has the problem
Hi all, I'm writing a script that uses rsync to sync 2 dirs on C7. I noticed a strange behaviour. I have 2 dir: src and dest. In src dir I generate a testfile with "dd if=/dev/zero of=testfile bs=1M count=100" and when I run "du -h testfile" I get the correct result. Then I sync src/ to dest/ using "rsync -avS? src/ dest/", all ok but when I run "du -h
2011 Mar 05
1
file mode lost in file.copy()?
Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname
2011 Mar 05
1
file mode lost in file.copy()?
Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname
2007 Nov 29
2
Overriding resources in a define in a module - can''t get syntax right
Maybe it works, maybe it doesn''t, but I sure as hell can''t make it work. I get stuck with "Could not find object(s)" whatever I do This is my module init.pp class ztest::setup { notice "MAIN SETUP CLASS" file { directfile: path => "/etc/directfile", owner => root, group => root, mode => 0644, content
2011 Jun 03
4
Problem using read.xls - Everything converted to factors
Hallo, I would like to use to read.xls function from the gdata package to read data from Microsoft Excel files but I experienced a problem: For example I used the following code: testfile<-read.xls("/home/.../wsjecon0603.xls", #file path header=F, dec=",", na.strings="n.a.", skip=5, sheet=2,
2020 Jan 15
2
[semi-OT] C7 Possible bug but I can't determine what tool has the problem
Il 15/01/20 17:51, Jon Pruente ha scritto: > On Wed, Jan 15, 2020 at 10:18 AM Alessandro Baggi < > alessandro.baggi at gmail.com> wrote: > >> I made several test to see what happens and noticed that removing -S >> (--sparse) from rsync command problem does not occour. >> In another test, thinking about a problem on 0ed file, I tried file >> generation using
2017 Feb 06
2
Regular users can't log in to Samba AD DC from Windows
Thank you, Rowland, for the reply. On 02/06/2017 10:44, Rowland Penny via samba wrote: > On Mon, 6 Feb 2017 10:07:18 +0200 > Alnis Morics via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I continue setting up my FreeBSD 11.0 machine with Samba 4.4.9 built >> from sources. (Actually, OS type and Samba version don't matter so >> much, as I
2012 Sep 13
1
[LLVMdev] Parsing C++ template parameters using cindex.py
Hi, I am parsing a C++ file using cindex.py and want to get the template parameters to a specific node. However, the tree seems to be different depending on if the template parameter is a struct/class or a simple type such as int or float. In the first case the template type is appended as a child to the VAR_DECL node (the TYPE_REF node seen in the example below), but this is not the case with