Re: Adding default for m64/m32 handle

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 26, 2012 at 12:45 AM, Dan Carpenter
<dan.carpenter@xxxxxxxxxx> wrote:
> Hi Chris,
>
> The patch 7aa79f8401f0 "Adding default for m64/m32 handle" causes
> a problem for variables called x86_64.
>
> $ echo "unsigned char x86_64;" > test.c
> $ ./sparse test.c
> test.c:1:15: warning: missing identifier in declaration
> test.c:1:15: error: Expected ; at the end of type declaration
> test.c:1:15: error: got 1

Are you suggesting we do some thing like this patch to remove the
define of x86_64?
Gcc does not seem to define x86_64.

Any objections?

Chris

diff --git a/lib.c b/lib.c
index b4d3944..bb814f2 100644
--- a/lib.c
+++ b/lib.c
@@ -372,8 +372,6 @@ static void handle_arch_m64_finalize(void)
                size_t_ctype = &ulong_ctype;
                ssize_t_ctype = &long_ctype;
 #ifdef __x86_64__
-               add_pre_buffer("#weak_define x86_64 1\n");
-               add_pre_buffer("#weak_define __x86_64 1\n");
                add_pre_buffer("#weak_define __x86_64__ 1\n");
 #endif
        }
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux