[ACTIVITY] Weekly report for weeks 47 & 48

=== Work done during the past 2 weeks === * GNU-296 (Fix stack protector on ARM): committed! * LLVM-432 (Support arithmetic on FileCheck regex variable): + finished reworking parsing code to be separate from evaluation and support more complex expression + fix compile errors and bugs

[ACTIVITY] Weekly report for weeks 45 & 46

=== Work done during the past 2 weeks === * Resurrect code size optimization for fmul/dmul from Tony Wang: bootstraping + rework slightly to better deal with switch of section and deal with several possible section layout + start anew with a new approach based on symbol visibility ->

[ACTIVITY] Weekly report for week 44

=== Work done during the past week === * Resurrect code size optimization for fmul/dmul from Tony Wang: + clean up new testsuite directive andd testcases * Fix -mslow-flash-data: + resurrect / rebase Arm internal patch to fix -mslow-flash-data once and for all + many fixes to make it pass

[ACTIVITY] Weekly report for week 43

=== Work done during this past week === * GNU-296 / GCC PR85434 / CVE-2018-12886: upstream review + avoid useless cmp after eors + fix another missing earlyclobber + full Thumb-1, Thumb-2 and Arm bootstrap with testing with and without -fPIC, with and without -fstack-protector-all *

[ACTIVITY] Weekly report for week 42

=== Work done during this past week === * GNU-296 / GCC PR85434 / CVE-2018-12886: + few more issues fixed and associated testing + now also running Thumb-1 bootstrap and testing * Prepare patch to further update cpus and architectures in bfd * Line management === Plan for week 43 === *

[ACTIVITY] Weekly report for week 41

=== Work done during this past week === * TCWG-1428 (Support arithmetic on FileCheck regex variable): + continued cleaning up code and painfully rebased it on recent trunk * GNU-296 / GCC PR85434 / CVE-2018-12886: + fixed changes to routines for PIC access to use specified register + fixed

[ACTIVITY] Weekly report for week 40

=== Work done during this past week === * One day annual leave * TCWG-1428 (Support arithmetic on FileCheck regex variable): + started cleaning up code and continued adding support for last syntax tweaks * TCWG-1379 / GCC PR85434 / CVE-2018-12886: rework needed + After more testing committed

[ACTIVITY] Weekly report for week 37 to 39

=== Work done during these past 3 weeks === * DSGHACK-25 (Support arithmetic on FileCheck regex variable): + all my tests pass, started to implement further minor changes to the syntax * PR87374: external review + investigate bug, write patch, test it and send for external review * GCC

[ACTIVITY] Weekly report for week 36

=== Work done during this 3-day week === * TCWG-1428 (Support arithmetic on FileCheck regex variable): + continue to rework patch, feature complete and most testcase pass + sent another external email to hammer a few details * Arm new starter welcome and related faff * GNU Tools Cauldron +

[ACTIVITY] Weekly report for week 34

Note: annual leave tomorrow and Friday, as per my calendar === Work done during 3-day week === * TCWG-1379 / GCC PR85434 / CVE-2018-12886: rework needed + fix 2 more issues with retesting each time * More knowledge transfer within Arm (writing a script to automate manual task in GNU Arm

[ACTIVITY] Weekly report for week 33

Note: I'll be on holidays Thursday and Friday next week. === Work done during 3-day week === * TCWG-1379 / GCC PR85434 / CVE-2018-12886: rework needed + heavy testing * TCWG-1337 / LLVM PR34170: get backport to LLVM 7 branch * create design review for -mfpu=auto option in GAS ->

[ACTIVITY] Weekly report for week 32

=== Work done during this week === * TCWG-1379 / GCC PR85434 / CVE-2018-12886: rework needed + fix issues seen on x86_64 and start a bigger round of testing * TCWG-1337 / LLVM PR34170: last patch committed to trunk + address review comments and commit it once approved, then request backport

[ACTIVITY] Weekly report for week 31

=== Work done during this week === * TCWG-1379 / GCC PR85434 / CVE-2018-12886: rework needed + commit and revert due to regression on x86 and in glibc for aarch64 -> seems there is at least 2 issues, *sigh* * TCWG-1337 / LLVM PR34170: + track down and fix issue that patch 2/3 uncovered,

[ACTIVITY] Weekly report for week 30

=== Work done during this 4day week === * Continued looking into MCF branch prediction overload due to too many consecutive branches: + managed to get reproducible results -> was missing --buildid-dir option when invoking perf -> above flag seems ignored if a binary with same path

[ACTIVITY] Weekly report for week 29

=== Work done during this 4.5day week === * TCWG-1062 (MCF branch prediction overload due to too many consecutive branches): + rework reproduction steps around an existing script that does all the steps of downloading and installing the benchmark and run it under perf + gather what was

[ACTIVITY] Weekly report for week 28

=== Work done during this week === * Continue work on TCWG-1428 (Support arithmetic on FileCheck regex variable): external review + finish adding comments + add documentation and testcase + respond to feedback and send email to llvm-dev to discuss best syntax for new feature * Started

[ACTIVITY] Weekly report for week 27

=== Work done during this week === * PR85434 / CVE-2018-12886 / TCWG-1379 (stack-protector failure on GCC ARM): external review + finish testing and patch clean up (comments + changelog) and submit for external review * Continue work on TCWG-1428 (Support arithmetic on FileCheck regex

[ACTIVITY] Weekly report for week 26

=== Work done during this 2.5day week === * 2.5 day off to take care of my sick son * stack-protector failure on GCC ARM: more testing needed + submitted CVE ID request -> will be known as CVE-2018-12886 once published + start testing * Continue work on DSGHACK-25 (Support arithmetic on

[ACTIVITY] Weekly report for week 25

=== Work done during this week === * stack-protector failure on GCC ARM: more testing needed + rework to introduce new standard pattern including guard's address computation and make pattern opaque until after register allocation + fill in form for new CVE ID and ask feedback on CVE

[ACTIVITY] Weekly report for week 17

=== Work done during this GCC week === * stack-protector failure on GCC ARM: need feedback from community + prevent CSE of stack protector's guard first by adding some extra UNSPEC then instead by making all memory accesses involved volatile + write 2 monstro regex (251 & 377 characters

[ACTIVITY] Weekly report for week 16

=== Work done during this GCC week === * TCWG-1379 (stack-protector failure on GCC ARM): need feedback from community + reproduce on trunk and find out why it happens on ARM and not AArch64 or x86 + find potential issue for all targets as well, though less likely + find discrepencies

[ACTIVITY] Weekly report for week 15

Note1: working for Linaro every other week === Issues === * IT issues made me loose 1 day of work === Work done during this LLVM+GCC week === * LLVM PR34170 (crashes with inline asm with double output operand in GPR): internal review + improved patch to also support case with several

[ACTIVITY] Weekly report for week 14

Note1: working for Linaro every other week Note2: had some important work to do on GCC this week so I'll do some LLVM work next week as well to catch up === Work done during this LLVM+GCC week === * LLVM PR34170 (crashes with inline asm with double output operand in GPR): upstream review +

[ACTIVITY] Weekly report for week 8

Note: working for Linaro every other week * start looking at fix for PR34170 / TCWG1137 (cannot select truncate in ARMv7 backend): + inline asm with >=64bit floating-point output is not handled + wrote a tentative patch which crashes later in the code, need to investigate * Start slides for

[ACTIVITY] Weekly report for week 4

Note: working for Linaro every other week == Progress == * PR35157 / TCWG-1308 (crash in ARM backend for VST1d64TPseudoWB_fixed instruction): + after 2 attempts got now a clean patch with no testsuite regression + need to add testcase and it will be good to go upstream * Track down why

Re: arm-eabi-g++: -isystem option handle header as c linkage

Hi Martin, In short yes, it is special behavior but I'm not sure that it is intended. Each target can opt in to *not* have -isystem implicitly wrap headers in extern C construct. Arm target does not do anything special and thus inherit that default behavior of implicit extern C, except when

[ACTIVITY] Weekly report for week 1 & 2

Hi everyone, Note 1: Working on Linaro 50% time. Note 2: had afternoons off for the first 2 weeks of January == Progress == * Week 1 (2/1 -> 5/1) working for Arm * Fix poor screen resolution issue * Onboarding process: + read all docs, setup accounts (gmail, octopus, ...) * PR35157 /