search for: redeclar

...evel1.c.obj In file included from C:/Users/clang/libunwind/src/UnwindLevel1.c:28: C:/Users/clang/libunwind/src/config.h:26:11: warning: keyword is hidden by macro definition [-Wkeyword-macro] #define static_assert(__b, __m) \ ^ C:/Users/clang/libunwind/src/UnwindLevel1.c:350:1: warning: redeclaration of '_Unwind_RaiseException' should not add 'dllexport' attribute [-Wdll-attribute-on-redeclaration] _Unwind_RaiseException(_Unwind_Exception *exception_object) { ^ C:/Users/clang/libunwind/include\unwind.h:174:5: note: previous declaration is here _Unwind_RaiseException(_Un...

...n order to get the ldap definitions (ldap.h etc) I've installed openldap 2.4.28. 3. Learning to hate '//' line comments :-) 4. I get the following error and the make stops [2358/3381] Compiling source3/passdb/pdb_ldap_util.c "/usr/include/stdio.h", line 528.12: 1506-343 (S) Redeclaration of fgetpos64 differs from previous declaration on line 323 of "/usr/include/stdio.h". "/usr/include/stdio.h", line 528.12: 1506-377 (I) The type "long long*" of parameter 2 differs from the previous type "long*". "/usr/include/stdio.h", line 53...

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 i...

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

..._____________ From: Eric Christopher <echristo at gmail.com> To: Pankaj Gode <godepankaj at yahoo.com>; Adrian Prantl <aprantl at apple.com> Cc: llvm Developers <llvmdev at cs.uiuc.edu> Sent: Monday, April 29, 2013 12:24 PM Subject: Re: [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:...

# 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 058f2e27476d xen/drivers/char/console.c --- a/xen/drivers/char/console.c Mon Aug 07 17:36:58 2006 -0500 +++ b/xen/drivers/char/conso...

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

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 compile...

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

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

...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...

...ntil the end of > the substatements controlled by the condition. If the > name is re-declared in the outermost block of a substatement > controlled by the condition, the declaration that re-declares > the name is ill-formed. Which gives us: while (int x=0) { int x=0; // error: redeclaration, clashes with condition } Both gcc and VC++ emit a compilation error for the above. Then the standard says this, 6.5.3p1: > names declared in the for-init-statement are in the same > declarative-region as those declared in the condition So names inside the 'for' loop clash w...

...and of course it would be good to fix this regression in 3.9.2 if there is one. --Jeremy --- ~ $ clang++-mp-3.9 -Wno-invalid-offsetof -c macho_relocatable_file.cpp In file included from src/ld/parsers/macho_relocatable_file.cpp:37: src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs 'int [1]' extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_6...

...t;> >>>> --- >>>> >>>> ~ $ clang++-mp-3.9 -Wno-invalid-offsetof -c macho_relocatable_file.cpp >>>> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >>>> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >>>> 'int [1]' >>>> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxReg...

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: redefinition of type %TO = type %TF ^ Also, what is the set of things that can be done with an as-yet unresolved opaque type? -- Rodney Bat...

...>> --- >>>>> >>>>> ~ $ clang++-mp-3.9 -Wno-invalid-offsetof -c macho_relocatable_file.cpp >>>>> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >>>>> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >>>>> 'int [1]' >>>>> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::...

...fixed in r280330 (in clang). Fred > > --Jeremy > > > --- > > ~ $ clang++-mp-3.9 -Wno-invalid-offsetof -c macho_relocatable_file.cpp > In file included from src/ld/parsers/macho_relocatable_file.cpp:37: > src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs > 'int [1]' > extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber > (int...

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

...>> >> --Jeremy >> >> >> --- >> >> ~ $ clang++-mp-3.9 -Wno-invalid-offsetof -c macho_relocatable_file.cpp >> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >> 'int [1]' >> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNumber &g...

...>>> >>> >>> --- >>> >>> ~ $ clang++-mp-3.9 -Wno-invalid-offsetof -c macho_relocatable_file.cpp >>> In file included from src/ld/parsers/macho_relocatable_file.cpp:37: >>> src/ld/parsers/libunwind/DwarfInstructions.hpp:920:13: error: redeclaration of 'compile_time_assert_failed' with a different type: 'int [((int)CFI_Parser<A>::kMaxRegisterNumber > (int)DW_X86_64_RET_ADDR) ? 1 : -1]' vs >>> 'int [1]' >>> extern int compile_time_assert_failed[ ( (int)CFI_Parser<A>::kMaxRegisterNu...