Tcwg-commits July 2024

tcwg-commits@lists.linaro.org

4 participants
11207 discussions

[toolchain/jenkins-scripts] reference refs/changes/29/44329/1 updated (c1f33f9fe -> 55ce830e3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/44329/1 in repository toolchain/jenkins-scripts. discards c1f33f9fe tcwg_gnu-build.sh: Rename tcwg_gnu_eabi* into tcwg_gnu_embed* adds 55ce830e3 tcwg_gnu-build.sh: Rename tcwg_gnu_eabi* into tcwg_gnu_embed* This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (c1f33f9fe) \ N -- N -- N refs/changes/29/44329/1 (55ce830e3) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/43529/1 updated (c141d3cf9 -> 34e72f562)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/43529/1 in repository toolchain/jenkins-scripts. discards c141d3cf9 wrappers/shadow-ar.sh: Rework option handling to handle bazel [...] adds 34e72f562 wrappers/shadow-ar.sh: Rework option handling to handle bazel [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (c141d3cf9) \ N -- N -- N refs/changes/29/43529/1 (34e72f562) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/43429/1 updated (b4edd4345 -> ed3505d9c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/43429/1 in repository toolchain/jenkins-scripts. discards b4edd4345 Do not "<output> | grep -q", use "<output> | grep -q ... >/de [...] adds ed3505d9c Do not "<output> | grep -q", use "<output> | grep -q ... >/de [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (b4edd4345) \ N -- N -- N refs/changes/29/43429/1 (ed3505d9c) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/43229/4 updated (407f66a62 -> 38b31d232)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/43229/4 in repository toolchain/jenkins-scripts. discards 407f66a62 tcwg_bmk-build.sh: Change board allocation adds 38b31d232 tcwg_bmk-build.sh: Change board allocation This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (407f66a62) \ N -- N -- N refs/changes/29/43229/4 (38b31d232) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/43229/3 updated (e1c7554a4 -> dd6ef8585)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/43229/3 in repository toolchain/jenkins-scripts. discards e1c7554a4 tcwg_bmk-build.sh: Change board allocation new dd6ef8585 tcwg_bmk-build.sh: Change board allocation This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (e1c7554a4) \ N -- N -- N refs/changes/29/43229/3 (dd6ef8585) 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 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: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/43229/2 updated (6d805d35d -> b9dc503ee)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/43229/2 in repository toolchain/jenkins-scripts. discards 6d805d35d tcwg_bmk-build.sh: Change board allocation adds b9dc503ee tcwg_bmk-build.sh: Change board allocation This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (6d805d35d) \ N -- N -- N refs/changes/29/43229/2 (b9dc503ee) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/43229/1 updated (2767820ff -> c8bc86b9f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/43229/1 in repository toolchain/jenkins-scripts. discards 2767820ff tcwg_bmk-build.sh: Change board allocation adds c8bc86b9f tcwg_bmk-build.sh: Change board allocation This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (2767820ff) \ N -- N -- N refs/changes/29/43229/1 (c8bc86b9f) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/42429/1 updated (f431414a1 -> ea1742b0b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/42429/1 in repository toolchain/jenkins-scripts. discards f431414a1 round-robin.sh: Fix if last emtpy lines in results file adds ea1742b0b round-robin.sh: Fix if last emtpy lines in results file This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (f431414a1) \ N -- N -- N refs/changes/29/42429/1 (ea1742b0b) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[toolchain/jenkins-scripts] reference refs/changes/29/42129/1 updated (76d07d67d -> 0b91a1ebd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to reference refs/changes/29/42129/1 in repository toolchain/jenkins-scripts. discards 76d07d67d dashboard-generate-squad.sh: Skip annotation when no change adds 0b91a1ebd dashboard-generate-squad.sh: Skip annotation when no change This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the reference 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 (76d07d67d) \ N -- N -- N refs/changes/29/42129/1 (0b91a1ebd) 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. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

[gcc] branch master updated (6a99f3ae962 -> 23f195b06ad)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 6a99f3ae962 modula2: Improve error message to include symbol name. new 23f195b06ad optabs/rs6000: Rename iorc and andc to iorn and andn 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/config/rs6000/rs6000-builtins.def | 44 +++++++++++++++++------------------ gcc/config/rs6000/rs6000-string.cc | 2 +- gcc/config/rs6000/rs6000.md | 4 ++-- gcc/doc/md.texi | 8 +++---- gcc/gimple-isel.cc | 12 +++++----- gcc/internal-fn.def | 4 ++-- gcc/optabs.def | 10 +++++--- 7 files changed, 44 insertions(+), 40 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

11 months, 2 weeks

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits July 2024