Re: Re: Re: Re: Getting info from used typedef

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

 



linux-sparse-owner@xxxxxxxxxxxxxxx schrieb am 21.01.2010 01:38:09:

> I took another look into it. I think if you are just working on the
> source code transform,
> you should be able to skip the evaluation step which short cut the 
typedef.
> 
> Can you try again with the same patch, but in your program, using
> __sparse(filename)
> instead of sparse(filename) to get the symbols? Using __sparse will skip 
the
> evaluation step. It should keep the typedef node unchanged.

Yes, that seems to help, thank you very much.
I think because of the missing evaluation step, it is now a little bit 
more tricky 
to get out the elements of an struct or enum, but it will work.
Do I lose anything else, skipping the evaluation step?

Is it possible to commit your change (
0001-hacking-preserve-typedef-name.patch) in source?
- I didn't recognize any change in behaviour when using the function 
sparse().


Regards
Tom


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