tcc does not follow the integer promotion rules on bit-fields.
For instance, consider the following code:
#include
union ui
{
struct
{
unsigned int manl:32;
unsigned int manh:20;
unsigned int exp:11;
unsigned int sig:1;
} s;
double d;
};
union ul
{
struct
Michael Matz wrote:
|On Mon, 6 Jun 2016, Steffen Nurpmeso wrote:
|I think this leaks memory when opath contains a string already. pbuf is
Indeed, pbuf comes from copy_linker_arg(), i sublimely overlooked
it, but indeed see now. I'm sorry.
--steffen
commit 2a28638 (HEAD -> refs/heads/i)
Au
Hi,
On Mon, 6 Jun 2016, Steffen Nurpmeso wrote:
> Bäh!
> Take this one, please, the other one deleted an option.
> Ciao!
I think this leaks memory when opath contains a string already. pbuf is
allocated memory, you free the opath, copy pbuf into npath, but then leak
pbuf itself (it's not leak
Bäh!
Take this one, please, the other one deleted an option.
Ciao!
--steffen
commit 2b59c82 (HEAD -> refs/heads/i)
Author: Steffen (Daode) Nurpmeso
AuthorDate: 2016-06-04 15:48:15 +0200
Commit: Steffen (Daode) Nurpmeso
CommitDate: 2016-06-06 13:59:30 +0200
Allow multiple -rpath link
Sorry, forgot the diff:
--steffen
commit db263ba (HEAD -> refs/heads/i)
Author: Steffen (Daode) Nurpmeso
AuthorDate: 2016-06-04 15:48:15 +0200
Commit: Steffen (Daode) Nurpmeso
CommitDate: 2016-06-06 13:37:03 +0200
Allow multiple -rpath linker arguments
---
libtcc.c | 26 +++
Good morning! :)
Michael Matz wrote:
|On Thu, 2 Jun 2016, Steffen Nurpmeso wrote:
|> Well, have i yet asked this? I think no...
|> It's like that for a long time, ever since i use tcc(1) (autumn
|> last year):
|>
|> ?0[steffen@wales tmp]$ cat t.c
|> #include
|> int main(void){
|>
Hello.
David Mertens wrote:
|Also, I am not sure what others think about the first line in which y\
|ou declare two integers and initialize them with the return values of\
| function
|calls. I guess that's fine, but I don't see it often in the codebase.\
| @Everyone, do we have a coding sta
