Tcwg-commits March 2016

tcwg-commits@lists.linaro.org

1 participants
813 discussions

[gcc] branch master updated (c97f5c9 -> 296a290)

by git

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from c97f5c9 gcc/ * config/i386/sse.md: Use vpbroadcastq for broad [...] new 296a290 2016-03-18 Christophe Lyon <christophe.lyon(a)linaro.org> The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/ChangeLog | 5 +++++ gcc/testsuite/gcc.target/aarch64/pr63304_1.c | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[toolchain/abe] branch benchmarking-paranoia updated (9489686 -> 71d4e3d)

by git

This is an automated email from the git hooks/post-receive script. bernie.ogden pushed a change to branch benchmarking-paranoia in repository toolchain/abe. discards 9489686 Suppress host key checking prompt discards 485ad31 ssh/rsync invocations take input from /dev/null discards 1187f97 Do not try to validate non-http(s) URLs discards 2329345 Check that only one of the paranoia cases is being employed discards 9ce72d5 Check that both or neither of the ssh-paranoia case values are set discards cc6065b Validate URLs requiring user/password auth discards 9ca200a Report response code when curl fails discards dfd97ef Guard against insecure credential transmission discards df9afea Make validation stages stand out clearly discards d7285c5 Split a pair of long lines into parts discards f5eba3f Support secret-passing for paranoid benchmarking discards 8509669 Move filesystem init to pre-exit-handler code new bd4d13b Move filesystem init to pre-exit-handler code new d590cfe Support secret-passing for paranoid benchmarking new 89a73ad Split a pair of long lines into parts new e0d9019 Make validation stages stand out clearly new 64f3698 Guard against insecure credential transmission new 4629f71 Report response code when curl fails new 4311445 Validate URLs requiring user/password auth new c03d67d Check that both or neither of the ssh-paranoia case values are set new 9e1feb2 Check that only one of the paranoia cases is being employed new aa26a93 Do not try to validate non-http(s) URLs new 29f8328 ssh/rsync invocations take input from /dev/null new 71d4e3d Suppress host key checking prompt This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (9489686) \ N -- N -- N refs/heads/benchmarking-paranoia (71d4e3d) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 12 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[toolchain/abe] branch benchmarking-paranoia updated (7fd2ee3 -> 9489686)

by git

This is an automated email from the git hooks/post-receive script. bernie.ogden pushed a change to branch benchmarking-paranoia in repository toolchain/abe. discards 7fd2ee3 Move filesystem init to pre-exit-handler code discards cd2a381 Suppress host key checking prompt discards 08ea9b0 ssh/rsync invocations take input from /dev/null discards 4afb1db Do not try to validate non-http(s) URLs discards 7c9309b Check that only one of the paranoia cases is being employed discards 853e0fb Check that both or neither of the ssh-paranoia case values are set discards f1597ce Validate URLs requiring user/password auth discards 090b684 Report response code when curl fails discards 8cc87eb Guard against insecure credential transmission discards 3b445ec Make validation stages stand out clearly discards b1939c7 Split a pair of long lines into parts discards 7d49c45 Support secret-passing for paranoid benchmarking new 8509669 Move filesystem init to pre-exit-handler code new f5eba3f Support secret-passing for paranoid benchmarking new d7285c5 Split a pair of long lines into parts new df9afea Make validation stages stand out clearly new dfd97ef Guard against insecure credential transmission new 9ca200a Report response code when curl fails new cc6065b Validate URLs requiring user/password auth new 9ce72d5 Check that both or neither of the ssh-paranoia case values are set new 2329345 Check that only one of the paranoia cases is being employed new 1187f97 Do not try to validate non-http(s) URLs new 485ad31 ssh/rsync invocations take input from /dev/null new 9489686 Suppress host key checking prompt This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7fd2ee3) \ N -- N -- N refs/heads/benchmarking-paranoia (9489686) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 12 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[toolchain/abe] branch benchmarking-paranoia updated (6aae0d8 -> 7fd2ee3)

by git

This is an automated email from the git hooks/post-receive script. bernie.ogden pushed a change to branch benchmarking-paranoia in repository toolchain/abe. discards 6aae0d8 Suppress host key checking prompt discards a16bce3 ssh/rsync invocations take input from /dev/null discards 1a68d4e Do not try to validate non-http(s) URLs discards 8757b6c Check that only one of the paranoia cases is being employed discards f8a9188 Check that both or neither of the ssh-paranoia case values are set discards 13bc58c Validate URLs requiring user/password auth discards 2680e6b Report response code when curl fails discards be7f8b3 Guard against insecure credential transmission discards a713df6 Make validation stages stand out clearly discards 32fcdf6 Split a pair of long lines into parts discards 1d46da4 Support secret-passing for paranoid benchmarking new 7d49c45 Support secret-passing for paranoid benchmarking new b1939c7 Split a pair of long lines into parts new 3b445ec Make validation stages stand out clearly new 8cc87eb Guard against insecure credential transmission new 090b684 Report response code when curl fails new f1597ce Validate URLs requiring user/password auth new 853e0fb Check that both or neither of the ssh-paranoia case values are set new 7c9309b Check that only one of the paranoia cases is being employed new 4afb1db Do not try to validate non-http(s) URLs new 08ea9b0 ssh/rsync invocations take input from /dev/null new cd2a381 Suppress host key checking prompt new 7fd2ee3 Move filesystem init to pre-exit-handler code This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (6aae0d8) \ N -- N -- N refs/heads/benchmarking-paranoia (7fd2ee3) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 12 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: config/bench/lava/host-session | 49 +++++++++++++++++------------------------- 1 file changed, 20 insertions(+), 29 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[gcc] branch gcc-5-branch updated (7744104 -> 96181a1)

by git

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gcc-5-branch in repository gcc. from 7744104 2016-03-18 Andre Vieira <andre.simoesdiasvieira(a)arm.com> new 96181a1 g++.dg/ext/pr57735.C should not run if the testsuite is expli [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/ChangeLog | 8 ++++++++ gcc/testsuite/g++.dg/ext/pr57735.C | 3 +++ 2 files changed, 11 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[gcc] branch master updated (666094f -> c97f5c9)

by git

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 666094f gcc/ new c97f5c9 gcc/ * config/i386/sse.md: Use vpbroadcastq for broad [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 5 +++++ gcc/config/i386/sse.md | 9 ++++++++- 2 files changed, 13 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[gcc] branch gcc-5-branch updated (c4b1374 -> 7744104)

by git

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gcc-5-branch in repository gcc. from c4b1374 Daily bump. new 7744104 2016-03-18 Andre Vieira <andre.simoesdiasvieira(a)arm.com> The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/ChangeLog | 7 +++++++ gcc/testsuite/gcc.target/arm/no-volatile-in-it.c | 1 + 2 files changed, 8 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[toolchain/abe] branch benchmarking-paranoia updated (333e0ce -> 6aae0d8)

by git

This is an automated email from the git hooks/post-receive script. bernie.ogden pushed a change to branch benchmarking-paranoia in repository toolchain/abe. discards 333e0ce Suppress host key checking prompt discards 6bc76f2 ssh/rsync invocations take input from /dev/null discards ac3d91b Do not try to validate non-http(s) URLs discards c00a947 Check that only one of the paranoia cases is being employed discards 8dd72a6 Check that both or neither of the ssh-paranoia case values are set discards 8187815 Validate URLs requiring user/password auth discards 0994706 Report response code when curl fails discards 856ab9c Guard against insecure credential transmission discards 672e756 Make validation stages stand out clearly discards e86475c Split a pair of long lines into parts discards e4f707d Support secret-passing for paranoid benchmarking new 1d46da4 Support secret-passing for paranoid benchmarking new 32fcdf6 Split a pair of long lines into parts new a713df6 Make validation stages stand out clearly new be7f8b3 Guard against insecure credential transmission new 2680e6b Report response code when curl fails new 13bc58c Validate URLs requiring user/password auth new f8a9188 Check that both or neither of the ssh-paranoia case values are set new 8757b6c Check that only one of the paranoia cases is being employed new 1a68d4e Do not try to validate non-http(s) URLs new a16bce3 ssh/rsync invocations take input from /dev/null new 6aae0d8 Suppress host key checking prompt This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (333e0ce) \ N -- N -- N refs/heads/benchmarking-paranoia (6aae0d8) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 11 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: scripts/Benchmark.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[toolchain/abe] branch benchmarking-paranoia updated (6b93775 -> 333e0ce)

by git

This is an automated email from the git hooks/post-receive script. bernie.ogden pushed a change to branch benchmarking-paranoia in repository toolchain/abe. discards 6b93775 Suppress host key checking prompt discards e918372 ssh/rsync invocations take input from /dev/null discards 497a40c Do not try to validate non-http(s) URLs discards 0912537 Check that only one of the paranoia cases is being employed discards 6a481d7 Check that both or neither of the ssh-paranoia case values are set discards 1c1138b Validate URLs requiring user/password auth discards 0aef17f Report response code when curl fails discards 078eb6a Guard against insecure credential transmission discards 7548e86 Make validation stages stand out clearly discards 6e733af Split a pair of long lines into parts discards 8aa7269 Support secret-passing for paranoid benchmarking new e4f707d Support secret-passing for paranoid benchmarking new e86475c Split a pair of long lines into parts new 672e756 Make validation stages stand out clearly new 856ab9c Guard against insecure credential transmission new 0994706 Report response code when curl fails new 8187815 Validate URLs requiring user/password auth new 8dd72a6 Check that both or neither of the ssh-paranoia case values are set new c00a947 Check that only one of the paranoia cases is being employed new ac3d91b Do not try to validate non-http(s) URLs new 6bc76f2 ssh/rsync invocations take input from /dev/null new 333e0ce Suppress host key checking prompt This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (6b93775) \ N -- N -- N refs/heads/benchmarking-paranoia (333e0ce) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 11 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: config/bench/lava/host-session-multilib.yaml | 5 ++++- config/bench/lava/host-session-no-multilib.yaml | 5 ++++- config/bench/lava/host-session-persist-safe.yaml | 5 ++++- 3 files changed, 12 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

[gcc] branch master updated (350514e -> 666094f)

by git

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 350514e Add testcases for pr70161 new 666094f gcc/ The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 7 +++++++ gcc/testsuite/ChangeLog | 5 +++++ gcc/testsuite/gcc.dg/pr70252.c | 16 ++++++++++++++++ gcc/tree-vect-stmts.c | 22 ++++++++++++++++++---- 4 files changed, 46 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/pr70252.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

8 years, 9 months

← Newer
1
...
30
31
32
33
34
35
36
...
82
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2016