== This Week ==
* TCWG-1005 (6/10)
- Trying to fix ICE with firefox
* Validation (2/10)
- Tweaking .gn files for building chromium
- patches to abe
- backport reviews
* Misc (2/10)
- Meetings
- bitwise-dce
== Next Week ==
- Continue ongoing tasks
___
== Progress ==
o Linaro GCC/Validation (6/10)
* Validation/Infra patch reviews
* Upstream monitoring job
* Release automation:
- Reworking tcwg-release.sh
o Misc (4/10)
* Various meetings and discussions.
== Plan ==
o Focusing on release automation and validation
__
== Progress ==
* Validation
- finally merged most of work of the past weeks
- main jobs are now using start-container scripts
- helped with new llvm build scripts and jobs
- abe initial config for gcc7: need to investigate a binutils build
problem in a trusty container
- improved tcwg-reg
Hello all,
I've been using GCC 4.9.4 for a while now (arm-linux-gnueabi-gcc (Linaro
GCC 4.9-2017.01) 4.9.4), and I found this strange behavior:
In the library header (libm5op.h):
-
#ifdef __cplusplus
extern "C" {
#endif
#include
void warm_and_run_(int64_t intervals_warm, int64_t intervals_
On Mon, Mar 27, 2017 at 8:30 AM, Fernando Endo wrote:
> I've been using GCC 4.9.4 for a while now (arm-linux-gnueabi-gcc (Linaro GCC
> 4.9-2017.01) 4.9.4), and I found this strange behavior:
> ...
> So, this means that warm_and_run_ is assumed by GCC 4.9.4 to have 32 bits
> arguments, while they a
