search for: redeclared

Displaying 20 results from an estimated 198 matches for "redeclared".

2020 Aug 15
5
Supporting libunwind on Windows 10 (32bit; 64bit) for MSVC and Clang
Hello. I was trying to compile https://github.com/llvm/llvm-project/tree/master/libunwind using: - MSVC - Clang I wasn't able to configure this project for using MSVC (directly or via clang-cl): >cmake -G Ninja -DLLVM_PATH="C:/Users/clang/llvm-project-10.0.1/llvm" -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX="C:\Users\clang\libunwind_llvm" ../libunwind --
2012 Oct 25
0
Compiling Samba4 RC3 on AIX 6.1 with IBM vac
Sorry - the first post got sent as a response to an unrelated thread :-( ........................... Hi, I'm trying to get a samba4 build on AIX 6.1, and run into a couple of problems: 1. The entire Kerberos Heindal #includes need to be explicity included(with path) 2. In order to get the ldap definitions (ldap.h etc) I've installed openldap 2.4.28. 3. Learning to hate '//'
2009 Mar 17
1
[PATCH 1/1] CORE/writedec: Fix overflow and redeclaration
From: Gene Cumm <gene.cumm at gmail.com> CORE/writedec: Fix overflow and redeclaration; If EDX is greater than or equal to 10, div can cause an overflow. Comment out declaration of writechr. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Against current head. hpa: If there's a preferred way to do what this function provides, let me know. Was the writechr in there on
2000 Dec 22
5
(HP-UX) scan: last line gets duplicated (PR#790)
The last line gets duplicated when a file is read like this: a <- scan(file=filename, what="", sep="\n", strip.white=c(TRUE), quiet=TRUE) (This error does not occur on Linux, the only other platform I tested.) Version: platform = hppa2.0-hp-hpux10.20 arch = hppa2.0 os = hpux10.20 system = hppa2.0, hpux10.20 Actually, all binaries are
2013 Apr 29
1
[LLVMdev] LowerDbgDeclare results in redeclaration of local variable
Hi Eric,   Thanks for patch information. I have checked the patch with my code and I see that it works. But when I extract the variable and check the metadata information to retrieve the scope information, I do not get exact scope, after optimization. As you said that this is a work in progress, so can we expect full version on this in llvm3.3 release ?   Regards, Pankaj  
2006 Aug 07
0
[PATCH] [XEN] Remove redundant redeclaration of ''machine_restart''
# HG changeset patch # User Hollis Blanchard <hollisb@us.ibm.com> # Date 1154990956 18000 # Node ID 058f2e27476d686538de2671f57c1ded5c693b47 # Parent 4196687234c530a11d26a199f1479bc07e08248f [XEN] Remove redundant redeclaration of ''machine_restart''. Fixes compile warning with gcc 3.4.2. Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com> diff -r 4196687234c5 -r
2013 Apr 29
0
[LLVMdev] LowerDbgDeclare results in redeclaration of local variable
There was a patch committed the other day that should, at least, work around some of the behavior you describe. Optimized debug info is an area that's being worked on in ToT and previous releases are particularly bad. I'd use that. -eric On Mon, Apr 29, 2013 at 7:02 AM, Pankaj Gode <godepankaj at yahoo.com> wrote: > Hi All, > > Due to 'LowerDbgDeclare' call ( as
2012 Feb 29
1
dovecot-2.1-pigeonhole-0.3.0 identifier redeclared: sieve_multiscript_run (patch)
Hi, I recently compiled dovecot-2.1.1 on Solaris 10 with Sun Studio, but when I want to compile Sieve for this version (dovecot-2.1-pigeonhole-0.3.0) I get an error: "sieve.c", line 578: identifier redeclared: sieve_multiscript_run and I see that declaration in sieve.h is different from definition in sieve.c, so compilation process fails with SunStudio cc compiler. I have done a quick hack to correct this, and then compiled successfully. Patch is included as attachment. Full output, OS and compiler...
2013 Apr 29
2
[LLVMdev] LowerDbgDeclare results in redeclaration of local variable
Hi All,   Due to 'LowerDbgDeclare' call ( as part of 'instruction combining' optimization), a local variable gets declared and initialized inside the basic blocks it is used in. Is there anyway I can avoid this ?   This is with reference with my previous question. http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/061644.html     Regards, Pankaj -------------- next part
2001 Sep 19
2
--with-acl-support
Dear Andrew Tridgell, i cant compile the 2.2.1-9 package --with-acl-support, beacuse HAVE_SYS_ACL_H has wrong settings somewhere. i cant fix the bug, i just comment out the #ifdef HAVE_SYS_ACL_H line in the source/include/includes.h for a (i hope) good compilation. i use acl 1.1.2 from sgi, and the latest debian woody packages. Regards. Imre Szollosi mailto:szollosi@elme.hu
2002 Nov 23
1
2.2.7 compile error using --with-acl-support on debian
...o.h:215: warning: data definition has no type or storage class include/proto.h:216: parse error before `sys_acl_get_fd' include/proto.h:216: warning: data definition has no type or storage class include/proto.h:217: parse error before `permset' include/proto.h:217: `sys_acl_clear_perms' redeclared as different kind of symbol include/vfs.h:117: previous declaration of `sys_acl_clear_perms' include/proto.h:218: parse error before `permset' include/proto.h:218: `sys_acl_add_perm' redeclared as different kind of symbol include/vfs.h:118: previous declaration of `sys_acl_add_perm'...
2008 Oct 02
0
[LLVMdev] MS C++ gives error C2371 on this code while (obviously)gcc compiles it fine
Jay Freeman (saurik) wrote: > gcc is correct. According to the ISO specification, the for-init-statement > is supposed to inject any variable names into the same declarative scope as > the condition of an equivalent restructuring of the loop in the form of a > while statement, which in turn fronts the declaration to an extra scope that > surrounds the /entire/ loop construct.
2016 Dec 23
2
3.9 regression with legacy static assert macros (bad type resolution)
3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: #define COMPILE_TIME_ASSERT( expr ) \ extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); I notice that the issue is fixed on current trunk. Does anyone know what revision introduced the fix? Can we get it
2016 Dec 27
2
3.9 regression with legacy static assert macros (bad type resolution)
It already shipped AFAIK: http://releases.llvm.org/download.html — Mehdi > On Dec 27, 2016, at 9:55 AM, Akira Hatanaka via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Can we still check patches into 3.9.1? > >> On Dec 24, 2016, at 1:47 AM, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote: >> >> >>> On Dec 23, 2016, at 11:17,
2015 Feb 22
2
[LLVMdev] Resolving an opaque type in llvm-assembly
According to the Assembly language reference: "In LLVM, opaque types can eventually be resolved to any type (not just a structure type)." But the only way I can think of to do so is to give it a type name, then later redeclare the name. But that gives an error: %TO = type opaque %TF = type i32 ( %TO* ) %TO = type %TF gives: $ llvm-as types1.ll llvm-as: types1.ll:3:1: error:
2016 Dec 27
3
3.9 regression with legacy static assert macros (bad type resolution)
+Tom : is there a plan for a 3.9.2? — Mehdi > On Dec 27, 2016, at 10:30 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > It already shipped AFAIK: http://releases.llvm.org/download.html > > — > Mehdi > >> On Dec 27, 2016, at 9:55 AM, Akira Hatanaka via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Can we still check patches into
2016 Dec 23
0
3.9 regression with legacy static assert macros (bad type resolution)
> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: > > #define COMPILE_TIME_ASSERT( expr ) \ > extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( (
2008 Oct 02
3
[LLVMdev] MS C++ gives error C2371 on this code while (obviously)gcc compiles it fine
gcc is correct. According to the ISO specification, the for-init-statement is supposed to inject any variable names into the same declarative scope as the condition of an equivalent restructuring of the loop in the form of a while statement, which in turn fronts the declaration to an extra scope that surrounds the /entire/ loop construct. VC++ seems to be scoping the variables as if they were
2016 Dec 24
2
3.9 regression with legacy static assert macros (bad type resolution)
> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: > > >> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: >> >> #define
2016 Dec 27
0
3.9 regression with legacy static assert macros (bad type resolution)
Can we still check patches into 3.9.1? > On Dec 24, 2016, at 1:47 AM, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote: > > >> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: >> >> >>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>>