Vincent Lefevre wrote:
Note that according to C99, a bit-field is a type ("unsigned int" here
is just a type specifier). Just like an array is not the same type of
the type of its elements. See 6.7.2.1p9 in C99:
A bit-field is interpreted as a signed or unsigned integer type
consisting of th
Hi, first issue comes after big commits made by Michael Matz on 2016-12-15.
More specifically,
2016-12-15 Michael Matz fix aliases on 64 bit was the very last commit without
error on RPi.
Next commit 2016-12-15 Michael Matz Fix more nocode_wanted jump problems
Generates this error:
Test: 82_no
On 2017-02-09 21:01:11 +, Thomas Preud'homme wrote:
> On jeudi 9 février 2017 18:40:13 GMT grischka wrote:
> > Vincent Lefevre wrote:
> > > The C standard says:
> > > 6.3.1.1 Boolean, characters, and integers
> > >
> > > [...]
> > >
> > > If an int can represent all values of the or
On Thu, Feb 09, 2017 at 01:35:31PM +0100, Vincent Lefevre wrote:
> If an int can represent all values of the original type (as
> restricted by the width, for a bit-field), the value is converted
> to an int; otherwise, it is converted to an unsigned int. These are
> called the integer promo
On jeudi 9 février 2017 18:40:13 GMT grischka wrote:
> Vincent Lefevre wrote:
> > The C standard says:
> > 6.3.1.1 Boolean, characters, and integers
> >
> > [...]
> >
> > If an int can represent all values of the original type (as
> > restricted by the width, for a bit-field), the val
Vladimir Vissoultchev wrote:
Basicly yes, it's only useful for someone who does not have gcc installed on
Windows but is using MS toolchain.
Let me try something as a last resort. I want to enhanced current
build-tcc.bat with more parameters to
1. be able to produce config.h (for pre-build st
Basicly yes, it's only useful for someone who does not have gcc installed on
Windows but is using MS toolchain.
Let me try something as a last resort. I want to enhanced current
build-tcc.bat with more parameters to
1. be able to produce config.h (for pre-build step)
2. compile libtcc1.a (for
Vincent Lefevre wrote:
The C standard says:
6.3.1.1 Boolean, characters, and integers
[...]
If an int can represent all values of the original type (as
restricted by the width, for a bit-field), the value is converted
to an int; otherwise, it is converted to an unsigned int. These a
Vladimir Vissoultchev wrote:
* can someone please check & possibly fix the MSVC solution files in
win32/VS2015? Otherwise I'm tempted to remove that folder.
Just fixed project files in mob to generate config.h from VERSION as a
pre-build task, so solution
should compile ok on fresh checkout
Hi,
On 2017-02-08 23:09:05 +, Thomas Preud'homme wrote:
> On mercredi 8 février 2017 20:15:10 GMT grischka wrote:
> > Anyone else any patches that that 0.9.27 should still have?
>
> I'd like to fix
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832759 (if it is
> indeed a bug, I haven't
> * can someone please check & possibly fix the MSVC solution files in
> win32/VS2015? Otherwise I'm tempted to remove that folder.
Just fixed project files in mob to generate config.h from VERSION as a
pre-build task, so solution
should compile ok on fresh checkout (w/o running build-tcc.bat
avih wrote:
> On the downside as a developer you need to delete the .expect file
> manually if you want it to be rebuilt.
I don't recall that to be the case. Do correct me if I'm wrong, but at
least with out of tree builds, running "configure && make && make test"
- does generate the expect
Sure, I always do ./configure.
I've just made a new test from a brand new checkout and error is gone.
For ARM32/64 I always do a clean checkout, I have the impression that failing
tests are new (and probably never tested before on RPi).
I'll try today or tomorrow to find the first commit that bre
13 matches
Mail list logo
