Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[gcc] branch master updated (c8373dc8bf1 -> 4341106354c)

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 c8373dc8bf1 Update .po files new 4341106354c Daily bump. 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 | 102 ++++++++++++++++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 18 ++++++++ gcc/po/ChangeLog | 6 +++ gcc/testsuite/ChangeLog | 36 ++++++++++++++++ libcpp/po/ChangeLog | 6 +++ libstdc++-v3/ChangeLog | 111 ++++++++++++++++++++++++++++++++++++++++++++++++ 7 files changed, 280 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (2e977d99013 -> 95ebc6fdec5)

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 binutils-gdb. from 2e977d99013 gdbserver/linux-low.cc: Fix a typo in ternary operator new 95ebc6fdec5 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch gdb-13-branch updated (812ca62301e -> a55702108f6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from 812ca62301e Automatic date update in version.in new a55702108f6 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch binutils-2_40-branch updated (1caea232828 -> 49bd26445a6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_40-branch in repository binutils-gdb. from 1caea232828 Automatic date update in version.in new 49bd26445a6 Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[linux] branch master updated (a93e884edf61 -> 8cbd92339db0)

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 linux. from a93e884edf61 Merge tag 'driver-core-6.3-rc1' of git://git.kernel.org/pu [...] new e66104096a56 dt-bindings: clock: Fix node descriptions in uniphier-cloc [...] new 3b67e62130df dt-bindings: reset: Fix node descriptions in uniphier-rese [...] new 3fa1306d6a7f dt-bindings: pinctrl: Fix node descriptions in uniphier-pi [...] new d3df7f06e2a6 dt-bindings: regulator: Fix node descriptions in uniphier- [...] new 8f31aa56efe6 dt-bindings: watchdog: Fix node descriptions in uniphier-w [...] new a1e616a5fccb dt-bindings: thermal: Fix node descriptions in uniphier-th [...] new 4278eabebc16 dt-bindings: phy: Fix node descriptions in uniphier-phy example new e8c650f62787 dt-bindings: nvmem: Fix node descriptions in uniphier-efus [...] new 75c7aaa66f5f dt-bindings: soc: socionext: Add UniPhier system controller new 0611adff8b3a dt-bindings: soc: socionext: Add UniPhier SoC-glue logic new ddbbb9766b85 dt-bindings: soc: socionext: Add UniPhier SoC-glue logic d [...] new 9fb31379f061 dt-bindings: soc: socionext: Add UniPhier peripheral block new b3ad9754505a dt-bindings: soc: socionext: Add UniPhier media I/O block new 6796f54e8143 dt-bindings: soc: socionext: Add UniPhier SD interface block new 0c00d8d315f0 dt-bindings: soc: socionext: Add UniPhier ADAMV block new 5993f6bd555e dt-bindings: soc: socionext: Add UniPhier DWC3 USB glue layer new 9e699b8985e6 dt-bindings: soc: socionext: Add UniPhier AHCI glue layer new ec201955a53b kbuild: Optionally enable schema checks for %.dtb targets new 8e5d0c68f23a of: overlay: Fix trivial typo new 00f2a08cd785 dt-bindings: memory-controllers: ti,gpmc: fix typo in description new a98bf9df1c33 of: base: use strscpy() to instead of strncpy() new 5314187a603b dt-bindings: interrupt-controller: Convert Synquacer EXIU [...] new 3db50cb6db77 dt-bindings: i2c: Convert Synquacer I2C to DT schema new 8ffbaa98ccf8 dt-bindings: ufs: qcom,ufs: document required-opps new 323b8d0ddb92 dt-binding: gpio: publish binding IDs under dual license new 37483c262365 dt-bindings: clock: qcom,videocc: correct clocks per variant new fe7ce2983ba5 dt-bindindgs: i2c: qcom,i2c-geni: document operating-points-v2 new 7e38085d9c59 dt-bindings: riscv: add SBI PMU event mappings new eb2b4ecf7299 of/irq: add missing of_node_put() for interrupt parent node new aa222f9311e1 dt-bindings: PCI: Convert Rockchip RK3399 PCIe to DT schema new 805e640e09b0 dt-bindings: soc: socionext,uniphier-soc-glue: Make child [...] new 21fd06dc4a34 dt-bindings: drop type for operating-points-v2 new 8da765cca292 dt-bindings: vendor-prefixes: document lineartechnology new dbc2af0ace20 dt-bindings: display: msm: Drop type from 'memory-region' new 0be465c61d46 dt-bindings: interrupt-controller: brcm,bcm7120-l2-intc: F [...] new 92ec34fecc5d dt-bindings: PCI: ti,j721e-pci-host: Simplify 'device-id' schema new 18b616d0c0ff dt-bindings: reserved-memory: Refine 'size' and 'alignment' types new 56f9168f5ec6 dt-bindings: ti,k3: Use common ti,k3-sci-common.yaml schema new a222d7d96b58 dt-bindings: phy: hisilicon: Fix 'hisilicon,eye-diagram-pa [...] new f3531d1acb4b dt-bindings: display: bridge: sil,sii8620: convert to dtschema new df4fdd0db475 dt-bindings: firmware: arm,scmi: Restrict protocol child n [...] new 20f6d4f2a474 of: make of_node_ktype constant new ec340077a847 scripts/dtc: Update to upstream version v1.6.1-66-gabbd523bae6e new f9b8556d5799 dt-bindings: usb: convert fcs,fusb302.txt to yaml new 33887fce47e1 dt-bindings: intel,ixp4xx-expansion-bus: split out periphe [...] new 770ba14bd7fc dt-bindings: reference MC peripheral properties in relevan [...] new 0c559bc8abfb dt-bindings: serial: restrict possible child node names new aeb9267eb6b1 of: reserved-mem: print out reserved-mem details during boot new 25eba1598c8e dt-bindings: Fix multi pattern support in DT_SCHEMA_FILES new 6ee7afbabcee of: reserved_mem: Use proper binary prefix new 9cbad37ce812 of: Add of_property_present() helper new 2f0cb4753dd2 of: Use of_property_present() helper new 16b0c7cad99e of: Use preferred of_property_read_* functions new 511f3aa71029 of: prepare to add processing of EXPECT_NOT to of_unittest_expect new 568a10bfffe8 of: add processing of EXPECT_NOT to of_unittest_expect new f381b31a80bc of: update kconfig unittest help new 74df14cd301a of: unittest: add node lifecycle tests new 23522dd7033a of: do not use "%pOF" printk format on node with refcount of zero new ec0b7e24d566 of: add consistency check to of_node_release() new d9194e009efe of: dynamic: add lifecycle docbook info to node creation f [...] new 65f81bbd9117 dt-bindings: arm: Add Cortex-A715 and X3 new 0305c98c9e15 dt-bindings: interrupt-controller: convert loongson,ls1x-i [...] new 64d666a7bd85 dt-bindings: sram: qcom,imem: document sm8450 new fb4b06f521c1 dt-bindings: drop Sagar Kadam from SiFive binding maintainership new b4858dc61647 of: dynamic: Fix spelling mistake "kojbect" -> "kobject" new 1ba7dfb905b3 dt-bindings: regulator: Add mps,mpq7932 power-management IC new 8395d932d24a Merge tag 'devicetree-for-6.3' of git://git.kernel.org/pub [...] new 659bf8e582fc dt-bindings: iommu: dart: add t8110 compatible new 3d68bbb81b1a iommu: dart: Add suspend/resume support new 510d4072df7f iommu: dart: Support >64 stream IDs new 0b459bcdc5a8 iommu: dart: Support a variable number of TTBRs per stream new a772a02c1834 iommu: dart: Fix DART_PARAMS1/2 bit define names new b76c68fcb440 iommu: dart: Support different variants with different registers new d8bcc870d99d iommu: dart: Add t8110 DART support new cf5c1c87c239 iommu/dart: Fix apple_dart_device_group for PCI groups new 9e6a1825aca8 iommu: dart: DART_T8110_ERROR range should be 0 to 5 new 53719876e064 iommu/exynos: Fix error handling in exynos_iommu_init() new c64074bfe2ab iommu/exynos: Abstract getting the fault info new 2f599c3ff4e6 iommu/exynos: Implement fault handling on SysMMU v7 new 1505e7215eb7 dt-bindings: iommu: renesas,ipmmu-vmsa: add r8a779g0 support new c2b83395e558 iommu/arm-smmu-qcom: Add SM8150 DPU compatible new 5fba66d42746 iommu/arm-smmu-qcom: Select identity domain for sc8280xp MDSS new 6bc6af375c70 dt-bindings: arm-smmu: Allow 3 power domains on SM6375 MMU500 new 11321f7763d0 dt-bindings: arm-smmu: Add sm8150-smmu-500 to the list of [...] new 6dbffe465b7c dt-bindings: iommu: qcom: Add Qualcomm MSM8953 compatible new d565d60d3da7 dt-bindings: arm-smmu: disallow clocks when not used new 0802999c9b7c dt-bindings: arm-smmu: document the smmu on Qualcomm SA8775P new 822765f44ec1 dt-bindings: arm-smmu: Document smmu-500 binding for SM6125 new eb9181a3ae60 dt-bindings: arm-smmu: Fix binding for SDX55 and SDX65 new 8a24401701aa Merge branch 'for-joerg/arm-smmu/bindings' into for-joerg/ [...] new 9e6132179a62 Merge tag 'arm-smmu-updates' of git://git.kernel.org/pub/s [...] new d82e6ae67ac2 iommu/vt-d: Remove include/linux/intel-svm.h new 557abbd60c16 iommu/vt-d: Remove unused fields in svm structures new 49cab9d2b846 iommu/vt-d: Remove users from intel_svm_dev new ec9ab12dee30 iommu/vt-d: Remove sva from intel_svm_dev new e06d24435596 iommu/vt-d: Set No Execute Enable bit in PASID table entry new 4db96bfe9d77 iommu/vt-d: Support size of the register set in DRHD new a6a5006dad57 iommu/vt-d: Retrieve IOMMU perfmon capability information new dc57875866ab iommu/vt-d: Support Enhanced Command Interface new 7232ab8b89e9 iommu/vt-d: Add IOMMU perfmon support new 46284c6ceb5e iommu/vt-d: Support cpumask for IOMMU perfmon new 4a0d4265659b iommu/vt-d: Add IOMMU perfmon overflow handler support new d8a7c0cf05a2 iommu/vt-d: Enable IOMMU perfmon support new 60b1daa3b168 iommu/vt-d: Fix error handling in sva enable/disable paths new 16a75bbe480c iommu/vt-d: Avoid superfluous IOTLB tracking in lazy mode new 194b3348bdbb iommu/vt-d: Fix PASID directory pointer coherency new 257ec2907419 iommu/vt-d: Allow to use flush-queue when first level is default new ba9bee7f59fd iommu/amd: Do not allocate io_pgtable_ops for passthrough domain new 080920e52148 iommu/amd: Fix error handling for pdev_pri_ats_enable() new 05d227efbd8d iommu/amd: Do not clear event/ppr log buffer when snp is enabled new b6b26d86c61c iommu/amd: Add a length limitation for the ivrs_acpihid co [...] new 18792e99ea2f iommu/amd: Do not identity map v2 capable device when snp [...] new 996d120b4de2 iommu/amd: Improve page fault error reporting new f451c7a5a3b8 iommu/amd: Skip attach device domain is same as new domain new 1b932ceddd19 iommu: Remove detach_dev callbacks new 6caeb33fa986 iommu: Add set_platform_dma_ops iommu ops new c1fe9119ee70 iommu: Add set_platform_dma_ops callbacks new dd8a25c557e1 iommu: Remove deferred attach check from __iommu_detach_device() new 8f9930fa0161 iommu: Remove detach_dev callback new d286a58bc8f4 iommu: Tidy up io-pgtable dependencies new 584d334b1393 iommu/ipmmu-vmsa: Remove ipmmu_utlb_disable() new bb649412d39f iommu/fsl_pamu: Fix compile error after adding set_platfor [...] new e251c21372c0 of: Introduce of_translate_dma_region() new af0d81357cc5 dt-bindings: reserved-memory: Document iommu-addresses new a5bf3cfce8cb iommu: Implement of_iommu_get_resv_regions() new 5cef282e295f iommu: dma: Use of_iommu_get_resv_regions() new 1369459b2e21 iommu: Add a gfp parameter to iommu_map() new 4dc6376af596 iommu: Remove iommu_map_atomic() new f2b2c051be62 iommu: Add a gfp parameter to iommu_map_sg() new 96d578088085 iommu/dma: Use the gfp parameter in __iommu_dma_alloc_nonc [...] new e787a38e31e5 iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map() new 2552d3a2292a iommu/intel: Add a gfp parameter to alloc_pgtable_page() new 2d4d767659ff iommu/intel: Support the gfp argument to the map_pages op new 4951eb262384 iommu/intel: Use GFP_KERNEL in sleepable contexts new d3b82825217a iommu/s390: Push the gfp parameter to the kmem_cache_alloc()'s new 429f27e36874 iommu/s390: Use GFP_KERNEL in sleepable contexts new ff489fe002ab Merge branch 'iommu-memory-accounting' into core new 189d496b48b1 iommu/exynos: Add missing set_platform_dma_ops callback new 4762315d1c97 iommu/of: mark an unused function as __maybe_unused new 4daa861174d5 iommu: Fix error unwind in iommu_group_alloc() new 2cc73c5712f9 iommu: Attach device group to old domain in error path new bedd29d793da Merge branches 'apple/dart', 'arm/exynos', 'arm/renesas', [...] new a13de74e4765 Merge tag 'iommu-updates-v6.3' of git://git.kernel.org/pub [...] new 17cde5e601b1 genirq/msi: Add msi_device_has_isolated_msi() new efc30a8f15a7 iommu: Add iommu_group_has_isolated_msi() new 6b1a7a00427c vfio/type1: Convert to iommu_group_has_isolated_msi() new 25fc417f7938 iommufd: Convert to msi_device_has_isolated_msi() new a5e72a6bac14 genirq/irqdomain: Remove unused irq_domain_check_msi_remap() code new dcb83f6ec1bf genirq/msi: Rename IRQ_DOMAIN_MSI_REMAP to IRQ_DOMAIN_ISOL [...] new f188bdb5f1df iommu/x86: Replace IOMMU_CAP_INTR_REMAP with IRQ_DOMAIN_FL [...] new bf210f793937 irq/s390: Add arch_is_isolated_msi() for s390 new b062007c63eb iommu: Remove IOMMU_CAP_INTR_REMAP new fc3873095a09 Merge branch 'isolated_msi' into iommufd.git for-next new 9fabbdf338b7 selftests: iommu: Fix test_cmd_destroy_access() call in user_copy new 84798f284994 iommufd: Add three missing structures in ucmd_buffer new fd9f2a912255 Merge branch 'iommu-memory-accounting' of ssh://gitolite.k [...] new c9a397cee9f5 vfio: Support VFIO_NOIOMMU with iommufd new bed9e516f118 Merge branch 'vfio-no-iommu' into iommufd.git for-next new b3551ead6163 iommufd: Make sure to zero vfio_iommu_type1_info before co [...] new b4ff830eca09 iommufd: Do not add the same hwpt to the ioas->hwpt_list twice new 939204e4df96 Merge tag 'v6.2' into iommufd.git for-next new 143c7bc6496c Merge tag 'for-linus-iommufd' of git://git.kernel.org/pub/ [...] new 1b8ba6e41f11 RDMA/hfi1: Fix doc for hfi1_free_ctxt new cab30a983525 RDMA/cxgb4: remove unnecessary NULL check in __c4iw_poll_cq_one() new ee84146c05ad RDMA/erdma: Fix refcount leak in erdma_mmap new cf6a05c8494a RDMA/hns: Fix refcount leak in hns_roce_mmap new bd99ede8ef2d RDMA/irdma: Remove extra ret variable in favor of existing err new 968606e252e3 RDMA/hns: Remove rq inline in kernel new 2bb185c68bf4 RDMA/hns: Add compatibility handling for only support user [...] new 1d91855304c2 RDMA/hns: Support cqe inline in user space new 8d037973d48c RDMA/core: Refactor rdma_bind_addr new ccae0447af0e RDMA/cma: Refactor the inbound/outbound path records process flow new 3c49eef38978 IB/hfi1: Remove redundant pageidx variable new a479433a6b7a IB/hfi1: Assign npages earlier new d8f4ab01c6d0 IB/hfi1: Consolidate the creation of user TIDs new 845127ed8717 IB/hfi1: Improve TID validity checking new ef90f0a1913e IB/hfi1: Split IB counter allocation new 892ede5a77f3 IB/hfi1: Update RMT size calculation new 1ec82317a1da IB/hfi1: Use dma_mmap_coherent for matching buffers new ccdbefcf661e RDMA/cxgb4: Replace 0-length arrays with flexible arrays new 1ca49d26afc2 Merge branch 'mlx5-next' into HEAD new 312b8f79eb05 RDMA/mlx: Calling qp event handler in workqueue context new 8067fd8b26bf RDMA/mlx5: Print error syndrome in case of fatal QP errors new ed73a505480d RDMA/erdma: Replace zero-length arrays with flexible-array [...] new 01798df19878 RDMA/irdma: Split MEM handler into irdma_reg_user_mr_type_mem new 693a5386eff0 RDMA/irdma: Split mr alloc and free into new functions new e965ef0e7b2c RDMA/irdma: Split QP handler into irdma_reg_user_mr_type_qp new 2f25e3bab00e RDMA/irdma: Split CQ handler into irdma_reg_user_mr_type_cq new ade58da2a73d RDMA/rxe: Cleanup mr_check_range new db4729a52519 RDMA/rxe: Move rxe_map_mr_sg to rxe_mr.c new f04d5b3d916c RDMA-rxe: Isolate mr code from atomic_reply() new d8bdb0ebca08 RDMA-rxe: Isolate mr code from atomic_write_reply() new 325a7eb85199 RDMA/rxe: Cleanup page variables in rxe_mr.c new 592627ccbdff RDMA/rxe: Replace rxe_map and rxe_phys_buf by xarray new a2a88b8e22d1 RDMA/mlx5: Don't keep umrable 'page_shift' in cache entries new 18b1746bddf5 RDMA/mlx5: Remove implicit ODP cache entry new b95845178328 RDMA/mlx5: Change the cache structure to an RB-tree new 73d09b2fe833 RDMA/mlx5: Introduce mlx5r_cache_rb_key new dd1b913fb0d0 RDMA/mlx5: Cache all user cacheable mkeys on dereg MR flow new 627122280c87 RDMA/mlx5: Add work to remove temporary entries from the cache new ef42520240aa RDMA/cxgb4: add null-ptr-check after ip_dev_find() new 65a8fc30fb67 RDMA/siw: Fix user page pinning accounting new 828cf5936bea RDMA/mlx5: Fix MR cache debugfs error in IB representors mode new 85f9e38a5ac7 RDMA/mlx5: Remove impossible check of mkey cache cleanup failure new 283861a4c52c RDMA/cxgb4: Fix potential null-ptr-deref in pass_establish() new 68e416255b29 RDMA/restrack: Correct spelling new 8e6e49ccf1a0 RDMA/mlx5: Check reg_create() create for errors new 9cd9842c4699 RDMA/irdma: Cap MSIX used to online CPUs + 1 new 91d088a03049 RDMA/umem: Remove unused 'work' member from struct ib_umem new 50a542a8accc RDMA/mlx5: Use rdma_umem_for_each_dma_block() new 4ca446b127c5 iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_ [...] new 5ff31dfcd6d2 Subject: RDMA/rxe: Handle zero length rdma new 876e480da2f7 RDMA/cma: Distinguish between sockaddr_in and sockaddr_in6 [...] new 72a03627443d RDMA/rxe: Remove rxe_alloc() new 89d42b8c85b4 RDMA/mana_ib: Fix a bug when the PF indicates more entries [...] new a77a52385e9a RDMA/rxe: Fix missing memory barriers in rxe_queue.h new 4b7296aa6c66 net/mlx5: Expose bits for querying special mkeys new a419bfb76320 net/mlx5: Change define name for 0x100 lkey value new 1b1e4868836a net/mlx5e: Use query_special_contexts for mkeys new 594cac11ab6a RDMA/mlx5: Use query_special_contexts for mkeys new 5ef17179da7b Merge mlx5-next into rdma.git for-next new d2225b838cca RDMA/irdma: Add support for dmabuf pin memory regions new a0d198f79a8d IB/hfi1: Fix math bugs in hfi1_can_pin_pages() new fd8958efe877 IB/hfi1: Fix sdma.h tx->num_descs off-by-one errors new 66fb1d5df6ac IB/mlx5: Extend debug control for CC parameters new 8cbd92339db0 Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linu [...] The 226 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: .../testing/sysfs-bus-event_source-devices-iommu | 37 + Documentation/devicetree/bindings/Makefile | 2 +- Documentation/devicetree/bindings/arm/cpus.yaml | 2 + .../bindings/ata/intel,ixp4xx-compact-flash.yaml | 1 + .../devicetree/bindings/clock/qcom,videocc.yaml | 59 +- .../bindings/clock/sifive/fu540-prci.yaml | 1 - .../bindings/clock/socionext,uniphier-clock.yaml | 39 +- .../bindings/display/bridge/sil,sii8620.yaml | 108 +++ .../bindings/display/bridge/sil-sii8620.txt | 33 - .../bindings/display/msm/dp-controller.yaml | 3 +- .../devicetree/bindings/display/msm/gpu.yaml | 2 +- .../bindings/display/tegra/nvidia,tegra20-dc.yaml | 3 +- .../bindings/display/tegra/nvidia,tegra20-dsi.yaml | 3 +- .../bindings/display/tegra/nvidia,tegra20-epp.yaml | 3 +- .../display/tegra/nvidia,tegra20-gr2d.yaml | 3 +- .../display/tegra/nvidia,tegra20-gr3d.yaml | 3 +- .../display/tegra/nvidia,tegra20-hdmi.yaml | 3 +- .../display/tegra/nvidia,tegra20-host1x.yaml | 3 +- .../bindings/display/tegra/nvidia,tegra20-mpe.yaml | 3 +- .../bindings/display/tegra/nvidia,tegra20-tvo.yaml | 3 +- .../bindings/display/tegra/nvidia,tegra20-vi.yaml | 3 +- .../devicetree/bindings/dma/ti/k3-udma.yaml | 9 +- .../devicetree/bindings/firmware/arm,scmi.yaml | 43 +- .../bindings/fuse/nvidia,tegra20-fuse.yaml | 3 +- .../devicetree/bindings/i2c/i2c-synquacer.txt | 29 - .../bindings/i2c/qcom,i2c-geni-qcom.yaml | 2 + .../bindings/i2c/socionext,synquacer-i2c.yaml | 58 ++ .../interrupt-controller/brcm,bcm7120-l2-intc.yaml | 3 +- .../interrupt-controller/loongson,ls1x-intc.txt | 24 - .../interrupt-controller/loongson,ls1x-intc.yaml | 51 ++ .../interrupt-controller/sifive,plic-1.0.0.yaml | 1 - .../socionext,synquacer-exiu.txt | 31 - .../socionext,synquacer-exiu.yaml | 53 ++ .../devicetree/bindings/iommu/apple,dart.yaml | 1 + .../devicetree/bindings/iommu/arm,smmu.yaml | 66 +- .../devicetree/bindings/iommu/qcom,iommu.txt | 1 + .../bindings/iommu/renesas,ipmmu-vmsa.yaml | 1 + .../intel,ixp4xx-expansion-bus-controller.yaml | 66 +- .../intel,ixp4xx-expansion-peripheral-props.yaml | 80 ++ .../memory-controllers/mc-peripheral-props.yaml | 1 + .../bindings/memory-controllers/ti,gpmc.yaml | 2 +- .../bindings/mmc/nvidia,tegra20-sdhci.yaml | 3 +- .../devicetree/bindings/mtd/mtd-physmap.yaml | 1 + .../bindings/nvmem/socionext,uniphier-efuse.yaml | 101 ++- .../bindings/pci/rockchip,rk3399-pcie-common.yaml | 69 ++ .../bindings/pci/rockchip,rk3399-pcie-ep.yaml | 68 ++ .../bindings/pci/rockchip,rk3399-pcie.yaml | 132 ++++ .../devicetree/bindings/pci/rockchip-pcie-ep.txt | 62 -- .../devicetree/bindings/pci/rockchip-pcie-host.txt | 135 ---- .../devicetree/bindings/pci/ti,j721e-pci-host.yaml | 14 +- .../devicetree/bindings/perf/riscv,pmu.yaml | 161 ++++ .../bindings/phy/hisilicon,hi3660-usb3.yaml | 3 +- .../bindings/phy/hisilicon,hi3670-usb3.yaml | 3 +- .../bindings/phy/socionext,uniphier-ahci-phy.yaml | 24 +- .../bindings/phy/socionext,uniphier-usb2-phy.yaml | 41 +- .../phy/socionext,uniphier-usb3hs-phy.yaml | 29 +- .../phy/socionext,uniphier-usb3ss-phy.yaml | 26 +- .../pinctrl/socionext,uniphier-pinctrl.yaml | 17 +- .../devicetree/bindings/power/power-domain.yaml | 3 - .../bindings/pwm/nvidia,tegra20-pwm.yaml | 3 +- .../devicetree/bindings/pwm/pwm-sifive.yaml | 1 - .../devicetree/bindings/regulator/mps,mpq7932.yaml | 68 ++ .../regulator/socionext,uniphier-regulator.yaml | 21 +- .../bindings/reserved-memory/reserved-memory.yaml | 101 ++- .../reset/socionext,uniphier-glue-reset.yaml | 23 +- .../bindings/reset/socionext,uniphier-reset.yaml | 52 +- .../devicetree/bindings/riscv/sifive,ccache0.yaml | 3 +- Documentation/devicetree/bindings/serial/8250.yaml | 1 + .../devicetree/bindings/serial/serial.yaml | 2 +- .../soc/socionext/socionext,uniphier-adamv.yaml | 50 ++ .../socionext/socionext,uniphier-ahci-glue.yaml | 77 ++ .../socionext/socionext,uniphier-dwc3-glue.yaml | 106 +++ .../soc/socionext/socionext,uniphier-mioctrl.yaml | 65 ++ .../soc/socionext/socionext,uniphier-perictrl.yaml | 64 ++ .../soc/socionext/socionext,uniphier-sdctrl.yaml | 61 ++ .../socionext,uniphier-soc-glue-debug.yaml | 68 ++ .../soc/socionext/socionext,uniphier-soc-glue.yaml | 114 +++ .../soc/socionext/socionext,uniphier-sysctrl.yaml | 104 +++ .../devicetree/bindings/soc/ti/k3-ringacc.yaml | 13 +- .../devicetree/bindings/sram/qcom,imem.yaml | 1 + .../thermal/socionext,uniphier-thermal.yaml | 15 +- .../devicetree/bindings/ufs/qcom,ufs.yaml | 3 + .../devicetree/bindings/usb/fcs,fusb302.txt | 34 - .../devicetree/bindings/usb/fcs,fusb302.yaml | 67 ++ .../devicetree/bindings/vendor-prefixes.yaml | 2 + .../bindings/watchdog/maxim,max63xx.yaml | 1 + .../bindings/watchdog/socionext,uniphier-wdt.yaml | 10 +- MAINTAINERS | 8 +- Makefile | 9 +- arch/arm/mm/dma-mapping.c | 11 +- arch/s390/include/asm/msi.h | 17 + arch/s390/include/asm/pci_dma.h | 5 +- arch/s390/pci/pci_dma.c | 31 +- .../gpu/drm/nouveau/nvkm/subdev/instmem/gk20a.c | 3 +- drivers/gpu/drm/tegra/drm.c | 2 +- drivers/gpu/host1x/cdma.c | 2 +- drivers/infiniband/core/cma.c | 300 +++---- drivers/infiniband/core/sa_query.c | 171 ++-- drivers/infiniband/hw/cxgb4/cm.c | 7 + drivers/infiniband/hw/cxgb4/cq.c | 2 +- drivers/infiniband/hw/cxgb4/restrack.c | 2 +- drivers/infiniband/hw/cxgb4/t4fw_ri_api.h | 26 +- drivers/infiniband/hw/erdma/erdma_hw.h | 4 +- drivers/infiniband/hw/erdma/erdma_verbs.c | 4 +- drivers/infiniband/hw/hfi1/chip.c | 59 +- drivers/infiniband/hw/hfi1/exp_rcv.h | 5 +- drivers/infiniband/hw/hfi1/file_ops.c | 81 +- drivers/infiniband/hw/hfi1/init.c | 2 +- drivers/infiniband/hw/hfi1/sdma.c | 4 +- drivers/infiniband/hw/hfi1/sdma.h | 15 +- drivers/infiniband/hw/hfi1/user_exp_rcv.c | 46 +- drivers/infiniband/hw/hfi1/user_pages.c | 61 +- drivers/infiniband/hw/hfi1/verbs.c | 81 +- drivers/infiniband/hw/hns/hns_roce_device.h | 19 +- drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 109 +-- drivers/infiniband/hw/hns/hns_roce_hw_v2.h | 3 +- drivers/infiniband/hw/hns/hns_roce_main.c | 17 +- drivers/infiniband/hw/hns/hns_roce_qp.c | 66 +- drivers/infiniband/hw/irdma/hw.c | 2 + drivers/infiniband/hw/irdma/verbs.c | 313 +++++--- drivers/infiniband/hw/mana/main.c | 22 +- drivers/infiniband/hw/mlx4/main.c | 8 + drivers/infiniband/hw/mlx4/mlx4_ib.h | 3 + drivers/infiniband/hw/mlx4/qp.c | 121 ++- drivers/infiniband/hw/mlx5/cmd.c | 45 +- drivers/infiniband/hw/mlx5/cmd.h | 3 +- drivers/infiniband/hw/mlx5/cong.c | 28 +- drivers/infiniband/hw/mlx5/main.c | 24 +- drivers/infiniband/hw/mlx5/mlx5_ib.h | 51 +- drivers/infiniband/hw/mlx5/mr.c | 490 +++++++++--- drivers/infiniband/hw/mlx5/odp.c | 67 +- drivers/infiniband/hw/mlx5/qp.c | 164 +++- drivers/infiniband/hw/mlx5/qp.h | 4 +- drivers/infiniband/hw/mlx5/qpc.c | 7 +- drivers/infiniband/hw/mlx5/srq.c | 2 +- drivers/infiniband/hw/mlx5/umr.c | 4 +- drivers/infiniband/hw/mlx5/wr.c | 2 +- drivers/infiniband/hw/usnic/usnic_uiom.c | 8 +- drivers/infiniband/sw/rxe/rxe.h | 38 + drivers/infiniband/sw/rxe/rxe_loc.h | 12 +- drivers/infiniband/sw/rxe/rxe_mr.c | 606 +++++++------- drivers/infiniband/sw/rxe/rxe_pool.c | 46 -- drivers/infiniband/sw/rxe/rxe_pool.h | 3 - drivers/infiniband/sw/rxe/rxe_queue.h | 108 ++- drivers/infiniband/sw/rxe/rxe_resp.c | 202 ++--- drivers/infiniband/sw/rxe/rxe_verbs.c | 115 ++- drivers/infiniband/sw/rxe/rxe_verbs.h | 32 +- drivers/infiniband/sw/siw/siw_mem.c | 23 +- drivers/infiniband/ulp/ipoib/ipoib_main.c | 2 +- drivers/infiniband/ulp/srp/ib_srp.c | 2 +- drivers/iommu/Kconfig | 18 +- drivers/iommu/amd/init.c | 16 +- drivers/iommu/amd/iommu.c | 94 ++- drivers/iommu/apple-dart.c | 632 +++++++++++---- drivers/iommu/arm/arm-smmu/arm-smmu-qcom.c | 2 + drivers/iommu/arm/arm-smmu/qcom_iommu.c | 23 - drivers/iommu/dma-iommu.c | 21 +- drivers/iommu/exynos-iommu.c | 216 +++-- drivers/iommu/fsl_pamu_domain.c | 6 +- drivers/iommu/intel/Kconfig | 11 + drivers/iommu/intel/Makefile | 1 + drivers/iommu/intel/dmar.c | 33 +- drivers/iommu/intel/iommu.c | 124 ++- drivers/iommu/intel/iommu.h | 115 ++- drivers/iommu/intel/irq_remapping.c | 3 +- drivers/iommu/intel/pasid.c | 20 +- drivers/iommu/intel/perfmon.c | 877 +++++++++++++++++++++ drivers/iommu/intel/perfmon.h | 64 ++ drivers/iommu/intel/svm.c | 90 +-- drivers/iommu/iommu-traces.c | 1 - drivers/iommu/iommu.c | 195 +++-- drivers/iommu/iommufd/Kconfig | 2 +- drivers/iommu/iommufd/device.c | 8 +- drivers/iommu/iommufd/iommufd_private.h | 2 + drivers/iommu/iommufd/main.c | 3 + drivers/iommu/iommufd/pages.c | 6 +- drivers/iommu/iommufd/vfio_compat.c | 107 ++- drivers/iommu/ipmmu-vmsa.c | 28 - drivers/iommu/msm_iommu.c | 6 +- drivers/iommu/mtk_iommu.c | 9 - drivers/iommu/mtk_iommu_v1.c | 4 +- drivers/iommu/of_iommu.c | 96 +++ drivers/iommu/omap-iommu.c | 6 +- drivers/iommu/rockchip-iommu.c | 1 - drivers/iommu/s390-iommu.c | 24 +- drivers/iommu/sprd-iommu.c | 16 - drivers/iommu/sun50i-iommu.c | 1 - drivers/iommu/tegra-gart.c | 6 +- drivers/iommu/tegra-smmu.c | 5 +- drivers/irqchip/irq-gic-v3-its.c | 4 +- drivers/media/platform/qcom/venus/firmware.c | 2 +- drivers/net/ethernet/mellanox/mlx4/qp.c | 14 +- drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 22 +- drivers/net/ipa/ipa_mem.c | 6 +- drivers/net/wireless/ath/ath10k/snoc.c | 2 +- drivers/net/wireless/ath/ath11k/ahb.c | 4 +- drivers/of/Kconfig | 14 +- drivers/of/address.c | 41 + drivers/of/base.c | 3 +- drivers/of/dynamic.c | 31 +- drivers/of/irq.c | 12 +- drivers/of/kobj.c | 2 +- drivers/of/of_reserved_mem.c | 10 + drivers/of/overlay.c | 2 +- drivers/of/platform.c | 7 +- drivers/of/property.c | 4 +- drivers/of/unittest-data/testcases_common.dtsi | 1 + drivers/of/unittest-data/tests-lifecycle.dtsi | 8 + drivers/of/unittest.c | 150 +++- drivers/remoteproc/remoteproc_core.c | 5 +- drivers/vfio/Kconfig | 2 +- drivers/vfio/container.c | 7 - drivers/vfio/group.c | 7 +- drivers/vfio/iommufd.c | 19 +- drivers/vfio/vfio.h | 8 +- drivers/vfio/vfio_iommu_type1.c | 25 +- drivers/vfio/vfio_main.c | 7 + drivers/vhost/vdpa.c | 2 +- include/acpi/actbl1.h | 2 +- include/dt-bindings/gpio/gpio.h | 2 +- include/linux/cpuhotplug.h | 1 + include/linux/dmar.h | 1 + include/linux/intel-svm.h | 16 - include/linux/iommu.h | 41 +- include/linux/iommufd.h | 12 +- include/linux/irqdomain.h | 29 +- include/linux/mlx4/qp.h | 1 + include/linux/mlx5/driver.h | 1 - include/linux/mlx5/mlx5_ifc.h | 22 +- include/linux/mlx5/qp.h | 2 +- include/linux/msi.h | 17 + include/linux/of.h | 30 +- include/linux/of_address.h | 2 + include/linux/of_iommu.h | 8 + include/rdma/ib_sa.h | 2 +- include/rdma/ib_umem.h | 1 - include/rdma/ib_verbs.h | 2 +- include/rdma/rdma_cm.h | 1 - include/rdma/restrack.h | 4 +- include/trace/events/iommu.h | 7 - include/uapi/rdma/hns-abi.h | 4 + kernel/irq/irqdomain.c | 39 - kernel/irq/msi.c | 27 + scripts/dtc/dtc-parser.y | 11 +- scripts/dtc/libfdt/fdt.h | 4 +- scripts/dtc/of_unittest_expect | 183 ++++- scripts/dtc/version_gen.h | 2 +- tools/testing/selftests/iommu/iommufd.c | 2 +- 248 files changed, 7182 insertions(+), 3200 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-event_source-devices-iommu create mode 100644 Documentation/devicetree/bindings/display/bridge/sil,sii8620.yaml delete mode 100644 Documentation/devicetree/bindings/display/bridge/sil-sii8620.txt delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-synquacer.txt create mode 100644 Documentation/devicetree/bindings/i2c/socionext,synquacer-i2c.yaml delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson [...] create mode 100644 Documentation/devicetree/bindings/interrupt-controller/loongson [...] delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/socionex [...] create mode 100644 Documentation/devicetree/bindings/interrupt-controller/socionex [...] rename Documentation/devicetree/bindings/{bus => memory-controllers}/intel,ixp4xx- [...] create mode 100644 Documentation/devicetree/bindings/memory-controllers/intel,ixp4 [...] create mode 100644 Documentation/devicetree/bindings/pci/rockchip,rk3399-pcie-common.yaml create mode 100644 Documentation/devicetree/bindings/pci/rockchip,rk3399-pcie-ep.yaml create mode 100644 Documentation/devicetree/bindings/pci/rockchip,rk3399-pcie.yaml delete mode 100644 Documentation/devicetree/bindings/pci/rockchip-pcie-ep.txt delete mode 100644 Documentation/devicetree/bindings/pci/rockchip-pcie-host.txt create mode 100644 Documentation/devicetree/bindings/perf/riscv,pmu.yaml create mode 100644 Documentation/devicetree/bindings/regulator/mps,mpq7932.yaml create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] create mode 100644 Documentation/devicetree/bindings/soc/socionext/socionext,uniph [...] delete mode 100644 Documentation/devicetree/bindings/usb/fcs,fusb302.txt create mode 100644 Documentation/devicetree/bindings/usb/fcs,fusb302.yaml create mode 100644 arch/s390/include/asm/msi.h create mode 100644 drivers/iommu/intel/perfmon.c create mode 100644 drivers/iommu/intel/perfmon.h create mode 100644 drivers/of/unittest-data/tests-lifecycle.dtsi delete mode 100644 include/linux/intel-svm.h -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (120fc4b5ad -> bddbd2b89f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 120fc4b5ad 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards dcc7ad40a5 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 5c317bcc74 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 8062a550f3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 19c6db9d0d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 123d6fc806 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 4f0ba6a70a 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards a432afb0c0 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 2a611b5321 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 7ce1d75aee 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards a3dfa14cf6 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 1d8a5c50e2 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 4190a2c71c 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 63e9bc9143 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards d5d8a1ef44 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards c9159ba282 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 27b6b4df48 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 6532210f85 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 726008c8d1 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 38b45fee86 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 66a1c897fa 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 33ae10fee5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 78916d6045 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 58028a1698 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 39838ce1f2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 8587804eea 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards e772858aa9 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 16e63a291f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 26463eb762 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 145763e119 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 635abc856a 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 05ef29f6e6 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards d5545fed7c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 9e8dbe4d45 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 83f31196ab 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards b518958f4b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 32e1077be2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 5e0d056179 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 9ac8319de3 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 098c38c15a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 37cfd33ad9 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 440db4c32f 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 1794a61106 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards cd34fd4030 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards d1f9e553a2 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards de00d1a400 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 5c87616477 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 0fe011d190 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 63cd51b32a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 9054f1a13c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards f85350ccf1 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 789aa6360a 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards ad2e400f61 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards dce2acab8e 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards c724292f87 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards cd4d0c7fb5 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 1439dc926e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards c852f58861 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 02e64867dc 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards f1d11c366d 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards f0eeff9595 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards fae988576f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 303a437442 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards a9bef55e99 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 4c18e76f34 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards cc4c2dd6f7 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 13c6e74e1a 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 379e7ba8b7 125: onsuccess: #614: 1: Success after linux: 12 commits discards 74a7d0fc05 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 9f02f3e832 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards e83f6ade24 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards c424104f0f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 0b997b0738 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 27c2c6a84e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 0bbb89083b 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 80c92fa52a 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards b2bb30fa6b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 61c43b4b70 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 87995fd898 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards dbc308c12a 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards 4a5ea0d51d 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards f958230dbd 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards d89e5793bf 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 1b0aa786c6 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 1e418d2558 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards cc99e3aa8e 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 8e93724cb4 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards c2b60bf6f4 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards d43095ae0d 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 452e58d928 103: onsuccess: #589: 1: Success after binutils: 3 commits discards d983453924 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 4137a63ab7 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards c6dadafa09 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 3fbfdb11cd 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards d1e941d90d 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 847cb2ccf0 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 3852977ab4 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards bed8279338 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards b5c9c522fa 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards fbc7a4ae69 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards d5cd205775 92: onsuccess: #575: 1: Success after linux: 34 commits new e54fab6cdf 92: onsuccess: #575: 1: Success after linux: 34 commits new 233dc7bc1d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 50e5119b88 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 02b53c9f16 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new e22cc2c0a5 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new a43c46f0c1 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 3fd6b5ea39 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 4baf1c1b87 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 79975a8212 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 737be80f6d 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new e2598a16d8 102: onsuccess: #586: 1: Success after binutils: 5 commits new 1844a0eefb 103: onsuccess: #589: 1: Success after binutils: 3 commits new c9df7158c6 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 6ecc5852ab 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 6bc22b94f0 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 69a888f3d2 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 40d236daf5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 1c81d5fd15 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new a45de76902 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new d044d1c1f2 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 27ddd58043 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 6904e1ba23 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new bbd7e2616c 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 63fb6007d0 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 5f097a8260 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new d33dd91d3e 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new d192dc145c 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 54641e7307 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new cf559fe672 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new fa7b9cff1c 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 83d5f8020f 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new e943be0ac5 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new a0490afc39 124: onsuccess: #612: 1: Success after binutils: 18 commits new 4ae0282cc4 125: onsuccess: #614: 1: Success after linux: 12 commits new 0e737fc4a7 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 4831f38102 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 4e6503bcca 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 1a178d0265 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 3e365d6db0 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 74ccf8bae2 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new eb14d37195 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new d0cb1d44e8 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 1927500785 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 9ea9961413 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 342a1402f9 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new e820183d6f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 48fbb138b2 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new bb1fc7c3c2 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new e5b8b384cb 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new 27fb96d778 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new a219925a43 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 1f49f3f9f6 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 6a80cde69d 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 481981e5c0 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 97979ac20f 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 5524c61389 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 2e044dbc1d 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 5a4acfae1a 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 148b11101b 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new bd04cb89a6 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 0c8e489433 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 23b8fe380b 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new e587867997 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 8d27d693ff 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new f3e83315dd 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 5d8c0dd884 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new c7316a66fc 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 681f290bb7 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new ad31c67f3b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 388d0a91bf 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 00c4723884 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 5ed9e2fbf8 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 6af5f429eb 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 9feb2f340a 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new fdebd8e182 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new b93daf2f31 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 357b7657f9 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new ee97df1e1a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 1d3ff7d617 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new e8e7266664 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new b489526432 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 41f2e2a6fc 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 66715d3a8d 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 32c843923e 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new db6142d76e 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new a0aa9d9db3 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 69688d5890 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new ee53065d69 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 1eeddea693 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 8801b8472f 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 73785913bd 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 9c95d8d17b 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new c49dd8c2ad 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 2799ede015 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new da1aacad38 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 7f183970aa 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 17373bf3a3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new b7f9b0970a 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new a72e08df16 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 2ea7d10ea8 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 5683c4f188 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new bddbd2b89f 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] 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 (120fc4b5ad) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 52748 -> 52408 bytes 04-build_abe-gcc/console.log.xz | Bin 236816 -> 237716 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 11872 -> 9632 bytes 07-build_abe-glibc/console.log.xz | Bin 235760 -> 236588 bytes 08-build_abe-gdb/console.log.xz | Bin 51112 -> 52108 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2032 -> 2020 bytes 11-check_regression/console.log.xz | Bin 18108 -> 23764 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 44 +- 11-check_regression/mail-body.txt | 165 +- 11-check_regression/results.compare | 84 +- 11-check_regression/results.compare2 | 9558 +++++++++++++++------------ 11-check_regression/results.regressions | 84 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 167 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 84 +- sumfiles/gdb.log.xz | Bin 2830820 -> 2728060 bytes sumfiles/gdb.sum | 10415 ++++++++++++++++++------------ 31 files changed, 11994 insertions(+), 8701 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (6658448fbc -> 0eb90bfb46)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards 6658448fbc 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards b8df9da1a0 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards b433c970ab 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards 32f1367562 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards 2819aa540c 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards dc1f98d81a 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards d3a0e24e33 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards a4b58d3375 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards 222a01a507 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards 00af57b357 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards 813224e55a 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 5f32bc9216 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 2ae47fc217 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards 13449af36f 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards 088098d167 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards 7563436527 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards d1d284ff2e 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 25a24c690a 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 524b189268 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 02295a574d 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards 4b172126d8 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards b3e6cf82e0 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards f1111b98f5 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards 65ef578aa3 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 3d282c7392 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards db5c4a866b 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards 659937c8f1 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 2659fe5e76 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 5bc8df2662 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards c4cd99401b 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards bbc6e2b533 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 5c686ed4c6 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards cc637195a9 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards ac14d170a1 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 8fbe35f3fa 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards b3b1bab269 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards ae061ac93e 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards f9db9d067a 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 2f74784c57 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards 3e3f8755fd 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards e093dd31af 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards 2bd7792207 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 56bc64164d 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 5f261e53f0 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards c497d67532 141: onsuccess: #559: 1: Success after gcc: 4 commits discards 63d8eafce4 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards 0b32b4d683 139: force: #557: 2: Success after gcc: 6 commits discards cdb51b44bc 138: onsuccess: #554: 2: Success after binutils: 10 commits discards ca7d09f3ca 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards 2a1f7c98f9 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards 05f620c1e4 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards 890d778fd4 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards fd9dd7df52 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards 4493849d9d 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards 06f8587721 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 1a3984f77d 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards 2b1c7d4fef 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 9b3f87b84f 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards c5a06fb91d 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards b69041025a 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards 37ea1bfa47 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards c201158d88 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards de2b633616 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards 098f942e95 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards 7437ae8a41 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 03da133849 120: onsuccess: #535: 1: Success after binutils: 10 commits discards 2626006718 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 4190510319 118: force: #533: 2: Success after binutils: 4 commits discards 0ff10af910 117: onsuccess: #531: 2: Success after gcc: 65 commits discards f39afb2a58 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 0b7fbf0199 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards e55a148c6c 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards 41444e553f 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 0db79a0c2b 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 9c38ef4189 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards 1ea18f848e 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards 047a724c93 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards 5f09e32e50 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards c2f064c50b 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards 39a9c0f291 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards 03a16bf305 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits discards 88c2adb5d0 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits discards c7b05ed98b 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits discards 1d96fb7025 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits discards 225427a612 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards 56e63dac4f 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits discards 2ade962fb0 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits discards 7608c84629 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits discards f83df88d92 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits discards 9b74b1a6e2 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits discards d5770f4410 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits discards 92aee01fed 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits discards ea91a390a1 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits discards 71ef591821 92: onsuccess: #499: 2: Success after binutils: 4 commits discards d43f7a481c 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits discards b3e20c1f78 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits discards 762907f961 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits discards dbe32555a2 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits discards e0fb364198 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits discards 657cd99898 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits discards a8d5663663 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits new c8b0ab0f49 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits new c04fe2d1a3 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits new 87539b9d39 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits new e3eec3b269 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits new 9a4bb60161 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits new 24b87fdbeb 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits new 5ad2380291 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits new ac0d420b3f 92: onsuccess: #499: 2: Success after binutils: 4 commits new 9800d15e1f 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits new 9f02c712fb 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits new 15da1027e8 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits new e127e2a702 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits new 6d503f8a4f 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits new e4a499d0cc 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits new 9ac66538ae 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits new 9c5a83c9d1 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits new fcf0002724 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new 51364aa7c3 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits new 549cc2fee2 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new 227a1ab962 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits new 93bd91a282 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new ab6fc7a6b0 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new f0095cd308 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new 1a35dc5891 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new 2942cf5cb5 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new f5434c0d6d 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new a931c688b0 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new bc31609b51 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 2f7f3a4426 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 68d11a40fe 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new c98e2f95e1 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new a32288e549 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 8d0708c91f 117: onsuccess: #531: 2: Success after gcc: 65 commits new 607cdc6f96 118: force: #533: 2: Success after binutils: 4 commits new cb16310759 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] new e257ba39c8 120: onsuccess: #535: 1: Success after binutils: 10 commits new ec610c9276 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 4684ebbaac 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new 4d14c7d190 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 2f3ac42b07 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new f0c238a051 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 0ab09a3143 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 7f57e503e2 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new df71944526 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new e98b3cf7fe 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 4def6a6be1 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 3a013309e1 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 28508bd383 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new effde4878c 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new c2aeec6333 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 3ba05d598b 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new 609376e122 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new bfe7943f2c 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 08e9ea2b72 138: onsuccess: #554: 2: Success after binutils: 10 commits new 9490a9e963 139: force: #557: 2: Success after gcc: 6 commits new 58dfdabbc5 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g3 [...] new 69ccf660fc 141: onsuccess: #559: 1: Success after gcc: 4 commits new e9feaadd14 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 2406541365 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new 8b825e9ae0 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new 0969c4fad0 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new 5e229df50e 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new b62da5a4cb 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new 0612f6e5a1 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new 5cb5512031 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new dd29b5c936 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new df3ecde422 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new 59a9a40d7d 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new b26b00e1f2 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new cba3dbe849 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new ff60c05fa6 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 7de47e3148 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new 4f568484a8 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new 2dcd9894a2 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new 51833a49b1 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new a729af16e9 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 53ccc3e1d7 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new b049a1bac9 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new cb2d7aaaa0 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 76ef2f41e2 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new 3f76dba27c 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new a1de61a130 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new ad3136b2bb 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 915f3ab9b7 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new f8f7b7a99d 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 3d088f8eb8 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 6c9c5e3dfc 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new 8d3679aaf7 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 28b34a81ec 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 4cb45f4aed 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new f33129f09a 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new 3f39acdb9e 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new f1d76f76a4 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new 1b0bcc3046 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new b21d126882 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 29bf51a96d 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 3135e64a37 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new 7f10d4a9c8 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 07208bff3e 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 753288f79e 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new 55a71d37b9 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 0eb90bfb46 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits 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 (6658448fbc) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1744 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 38640 -> 38996 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 516676 -> 520744 bytes 06-check_regression/console.log.xz | Bin 3032 -> 3128 bytes 07-update_baseline/console.log | 38 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++------ 13 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (eaf5d92c01 -> 53c4aa595a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards eaf5d92c01 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards d766cec4c3 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 30ab3aa84a 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 615b4f3dcf 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 7c753db49d 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards f7e59e4759 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards fdda783563 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 4091937df0 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards ca8616db95 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards a3519c9ddd 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 4b0451777e 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards d877be6fe9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 4b64979b61 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards d3b10dc187 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards b099ae732d 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards d25bd4573e 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards f9f691ca8a 408: onsuccess: #2662: 1: Success after linux: 11 commits discards 5ae3d1b0b2 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 58dcf35e66 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 3611527d2d 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards cc2e9e56df 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards edb0ee109e 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards ce734434b7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards f5906f2efe 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards dafb13f4bd 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards a13594a931 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards efffec22ef 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards c347bd46df 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards c71d75da3c 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards bd83c69dc5 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 4e27ae47af 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards 8a97e7b49c 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 562fcaaa39 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards a3ba80d54f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 8f9a7a8984 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 2f8a7496ef 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards cf00408ee9 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards c1ff721d39 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards aaab044c28 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards e2e6513cf9 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 5ae1da5cbe 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 3be70da5a5 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards abc59c80a6 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 6c87cfdacc 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 3308f07aab 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards d0dbc12a4b 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] discards 6ede603199 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards fef79c2c36 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards d316a7d759 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 80843f45d2 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards bf487234ba 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 2a238246af 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards 85c602c3e6 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards 57b0247659 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards 902cc19755 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards b859501f12 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 64cca71f2d 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards 0ecfd45b53 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards 675d2a61a7 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards 517b5cd6b1 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 0ddffe83f2 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 8953053f80 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards ac21cca516 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards c8a665a915 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 3856a8e7ac 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 7acf127e2d 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 9567f08645 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 4c2eccc105 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards d476f4a3e4 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 9f304afc8b 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 473c67bfb1 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 04b7024ebd 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 7347586982 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards e72a555308 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 29c7b95497 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 33e40cb636 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards bb610a1f09 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ea6fabfefa 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 099007a9b4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 89367df106 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 7235436031 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ed507a208b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards d873519e95 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards ef31a9b070 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 5f5a304541 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards beb4089bc7 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards a5f6c5c1ef 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 0c193fb207 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 86ee04c40a 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 49e75a728b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 905f796ab1 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards a676957b98 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 92c5e3b61a 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 595c107bbd 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards a876543892 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards c71a934b49 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 1c2d0d4a65 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 4b65b67241 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 4993d7aaf8 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 05dd1062a5 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards d2c034f409 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new b948073e92 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 09e578b922 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 6fc02514ad 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 5dd95c04df 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 0ea944a8a5 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 5d3bc64734 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 89f90ef898 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new d49262508c 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 93388fbaf5 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new ac0109f05f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 3f5abf2f59 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new d3de09e1ee 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new b9089892fb 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new e3183d4a08 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 6cf02bd0f8 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 28c4d5f85d 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 1770a8c2e9 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new e9259f9835 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 5a2d719d86 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new a112bbb71d 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 804b105018 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 29f4354356 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 56b7a3e830 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new eb465e5806 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new fa954d619f 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new f6880607af 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new ebc22e4d8e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new aff847cfc9 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 6d75a065f8 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new fb4cf60331 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 81214095ff 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 23dd0b73ea 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new a21f2f1adb 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 5e9e81ab1c 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new bceef196e8 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 30256ba474 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 64c4773692 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 8e0a1623f0 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 6ebb1ce61a 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new a0641cc7bf 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 2900c07578 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 84347b8516 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new f85584158c 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new caa8f947da 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 4a59e1974c 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 7ab0010bed 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new b4c94c8483 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 442ab9b23b 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new d62e58aa00 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 58886d2bb7 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new 9217ccbe9a 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 42cf793412 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new ab85418dfe 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new 4eb0b1c0eb 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 20b6e02cf3 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new c4b37a0c30 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 5d5e7598b2 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 39caf0494d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 295973ed3d 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 564551664d 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new a78a5256dc 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new e02ffa8847 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new ab5741ff26 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new bfbc37a620 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 0c14437201 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new e40906f897 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 93b3addf3e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new ac54fc9c2e 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 89c149c3cc 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new ecfdb561c4 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new aee243da8e 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 59b029a595 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new c2fd62df77 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new 711b357e09 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 1e3d76ded6 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 33bd26494e 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 463b724045 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 29281d9662 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 9b3f828664 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 42272445f6 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 3b1819abd8 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new a291fc4333 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new dcb826fc87 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 472b46cd12 407: onsuccess: #2661: 1: Success after gcc: 7 commits new a1490d5e7c 408: onsuccess: #2662: 1: Success after linux: 11 commits new d00b71f30a 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new 5ab51ae012 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new cbd35434fa 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 4908de1b9b 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 74548bead9 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new 22a2194145 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 6ce28f2fc3 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new faa6cd7841 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 238052c299 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 36b4a452e3 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new ec0ffcc564 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 55317dd558 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 8596cca21a 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 92178fdcef 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new cd511c9336 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 1d68e04c0b 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 53c4aa595a 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] 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 (eaf5d92c01) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1824 -> 1820 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31252 -> 31012 bytes 04-build_abe-stage1/console.log.xz | Bin 70896 -> 71328 bytes 06-build_abe-linux/console.log.xz | Bin 9160 -> 9132 bytes 07-build_abe-glibc/console.log.xz | Bin 244136 -> 243836 bytes 08-build_abe-stage2/console.log.xz | Bin 202684 -> 202752 bytes 09-build_abe-gdb/console.log.xz | Bin 38912 -> 38644 bytes 10-build_abe-qemu/console.log.xz | Bin 31632 -> 31936 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2932 -> 2688 bytes 13-check_regression/console.log.xz | Bin 7068 -> 7144 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 10 ----- 13-check_regression/mail-body.txt | 42 ++++++++++---------- 13-check_regression/results.compare | 9 ++++- 13-check_regression/results.compare2 | 67 ++++++++++---------------------- 13-check_regression/results.regressions | 30 -------------- 14-update_baseline/console.log | 64 +++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 ++++++++++----------- mail/mail-subject.txt | 2 +- manifest.sh | 44 ++++++++++----------- results | 30 -------------- sumfiles/g++.log.xz | Bin 3406076 -> 3402216 bytes sumfiles/gcc.log.xz | Bin 3030132 -> 3031604 bytes sumfiles/gcc.sum | 6 +-- sumfiles/gfortran.log.xz | Bin 1048116 -> 1041128 bytes sumfiles/libatomic.log.xz | Bin 2316 -> 2312 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217476 -> 217484 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2680 -> 2680 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 439352 -> 438180 bytes sumfiles/libstdc++.sum | 24 +++++------- 42 files changed, 148 insertions(+), 245 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (7632f73c28 -> d202727733)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 7632f73c28 449: onsuccess: #4: 7: Success after binutils/gcc/gdb/qemu: [...] discards cd511b5c87 448: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] discards 1a6a6509b2 447: onsuccess: #2149: 7: Success after binutils/gcc/glibc/g [...] discards 25bf05bd1f 446: onsuccess: #2: 7: Success after binutils/gcc/linux/gdb: [...] discards 046fbf3cdd 445: onsuccess: #2148: 7: Success after binutils/gcc/linux/g [...] discards 6f8fd79ab8 444: onsuccess: #1: 7: Success after binutils/gcc/gdb: 11 commits discards 3d2c0165bf 443: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 12 [...] discards 67c9ae3aa2 442: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards 28f627310d 441: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards 51fb6ffca0 440: onsuccess: #2144: 7: Success after binutils/gcc/glibc/g [...] discards d15d6dcd6c 439: onsuccess: #2143: 7: Success after gcc: 7 commits discards 87ae93e7ef 438: onsuccess: #2142: 7: Success after binutils/linux/gdb: [...] discards e0aaafdc8b 437: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards 7fe3d6ab5b 436: onsuccess: #2140: 7: Success after binutils/gcc/linux/g [...] discards 8f1543d648 435: onsuccess: #2139: 7: Success after binutils/gcc/gdb/qem [...] discards 35fba2122a 434: onsuccess: #2138: 7: Success after binutils/gcc/linux/g [...] discards a5c4036d04 433: onsuccess: #2137: 7: Success after binutils/gcc/linux/g [...] discards 5311045337 432: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards 061fbc8692 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc/g [...] discards 9554b74766 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits discards 238782352d 429: onsuccess: #2133: 7: Success after binutils/gcc/linux/g [...] discards 11df61f9c7 428: onsuccess: #2132: 7: Success after binutils/linux/gdb: [...] discards 382361866b 427: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards 72b7bc6ed7 426: onsuccess: #2130: 7: Success after gcc: 7 commits discards c7fb893bc8 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits discards 17ac28ef22 424: onsuccess: #2128: 7: Success after binutils/gcc/linux/g [...] discards b0d855a434 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc/g [...] discards 46d3a4ed74 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits discards b35eea1302 421: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards 8064adc78f 420: onsuccess: #2124: 7: Success after binutils/gcc/linux/g [...] discards 9deb041173 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/qem [...] discards 69f25ef8b5 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/qem [...] discards bc3119e8a9 417: onsuccess: #2121: 7: Success after binutils/gcc/linux/g [...] discards 2438288d56 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc/g [...] discards 4ee0a96c27 415: onsuccess: #2119: 7: Success after gcc: 37 commits discards 69b88f0e2c 414: onsuccess: #2118: 7: Success after binutils: 5 commits discards 4aec2eb159 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits discards a315531b6e 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc/g [...] discards add1c543e0 411: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards 55f592fcef 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc/g [...] discards d0506b5d52 409: onsuccess: #2112: 7: Success after gcc: 3 commits discards a5a596fd07 408: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 3c8025a465 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc/g [...] discards fec9830c56 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] discards 9522e94587 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits discards 7ae1524421 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 2016992d13 403: onsuccess: #2106: 7: Success after glibc: 12 commits discards 65333d7062 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] discards 547faee0af 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] discards 106803782d 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 08a66a9778 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards 7b0d374175 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards 60b53abbe4 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 5da9fffde5 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards 0688b23f37 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards ba54994cc5 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards f9c3a6ae55 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards 914b89c1cf 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards 4740aebbdd 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards bc454dd0ce 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards 66c3d10a83 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 52dc79ac69 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 80f432eaf3 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards fd641cf48d 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 70549cf829 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards f954380bb8 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards 63474f6cbd 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 24e86ae003 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 22357caf77 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 6d9c3a2c88 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 52c8cbb7fa 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards d5afc12482 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 28fb7557a9 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards c406626d3c 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 8f677af65f 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 404370c502 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 6216d7b041 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards f98668ceb0 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 5016417271 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards 97c4dd23fa 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 68eb171723 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards c2f27db7a9 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards b5258cad0c 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 309095175e 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards a8049788a7 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 0e3cf25ea8 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 7d35dded17 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 82a0c32803 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards debc946f1c 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 4372788168 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 558ea56d35 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards e6d1bf5fd5 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards a55f637477 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 0d6d6bd186 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards 3e88325c2a 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 253eff1715 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 306ab4dabe 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards 296a80cfcd 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 88aca50824 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 8cfba2d268 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards db69fc0d70 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new cfc5af2f3d 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 734162dc07 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 6800175537 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 3b50924afe 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new 6097af349b 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new d83d0dc105 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new 13d23afb89 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new f5997597c2 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new b3b223670d 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new e41294b699 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new 5758eb28d9 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 29c20a6381 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 84baa127b2 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new fa4d3624c8 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 509956073c 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new c358485fec 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 9f4c75bd96 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new 0655b8d991 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new cfa6faa121 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 9ca3b4dbd4 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 03e4846374 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new b67ac139ff 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new e8bb08b3f9 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new e2b69a2818 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 7345f30059 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 722f718464 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new dc370cba6a 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new e482d8f13c 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 7e217fe66c 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new e5076e823c 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new b7de19ad2f 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 9f090055a5 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new 1989860b4e 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new 32d045e146 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 3b32591ace 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 2591587db6 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new d03c858b2f 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new 64a9c1ef46 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 632e2f72f6 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 1bf0ab2aa0 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 8d13690529 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new 850bdd54ab 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new 36fb3e6a73 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new 4014e40a73 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 98dd55e2dd 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new 2ec682b145 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 882dc58360 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new 26879b7046 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new b8ad561543 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new ab5e8d5061 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new cdb850e56b 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new 7d2ac3c97b 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new d0a7fb088e 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] new d31ccbc34e 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] new e46a13fd56 403: onsuccess: #2106: 7: Success after glibc: 12 commits new 781e971b4c 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new f94d3114a2 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits new 338c88b824 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] new 584f6e9bb4 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc/g [...] new 2e4d0c058d 408: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new 462390eded 409: onsuccess: #2112: 7: Success after gcc: 3 commits new af9cc7d089 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc/g [...] new 9dbc51d2a8 411: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new c35137f506 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc/g [...] new 5b1a3ede8e 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits new 1866f44f7a 414: onsuccess: #2118: 7: Success after binutils: 5 commits new c2539b8cfe 415: onsuccess: #2119: 7: Success after gcc: 37 commits new 1fa92a7aae 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc/g [...] new 8f5ddfd811 417: onsuccess: #2121: 7: Success after binutils/gcc/linux/g [...] new affcc0c707 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/qem [...] new 0e2c8bf168 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/qem [...] new 2cc95334b8 420: onsuccess: #2124: 7: Success after binutils/gcc/linux/g [...] new 8c9204cb47 421: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 6b7a51c580 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits new 39b6ea5bca 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc/g [...] new f202debf22 424: onsuccess: #2128: 7: Success after binutils/gcc/linux/g [...] new b140e8780b 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits new f21a2d308c 426: onsuccess: #2130: 7: Success after gcc: 7 commits new 6907f5dd9d 427: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new 677075e982 428: onsuccess: #2132: 7: Success after binutils/linux/gdb: [...] new d13987d7e8 429: onsuccess: #2133: 7: Success after binutils/gcc/linux/g [...] new c275acda89 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits new 2fc0050976 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc/g [...] new dfc013f00a 432: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new 170de5fbf7 433: onsuccess: #2137: 7: Success after binutils/gcc/linux/g [...] new 074b49a0de 434: onsuccess: #2138: 7: Success after binutils/gcc/linux/g [...] new 27fc109f7a 435: onsuccess: #2139: 7: Success after binutils/gcc/gdb/qem [...] new 6d92fd6fbf 436: onsuccess: #2140: 7: Success after binutils/gcc/linux/g [...] new 5657cc63ad 437: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new 76b3f8d65b 438: onsuccess: #2142: 7: Success after binutils/linux/gdb: [...] new a212b6a528 439: onsuccess: #2143: 7: Success after gcc: 7 commits new e9417376ef 440: onsuccess: #2144: 7: Success after binutils/gcc/glibc/g [...] new c9edbdcaf5 441: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 5dcbcb55c4 442: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new 316ae263c6 443: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 12 [...] new e726e70470 444: onsuccess: #1: 7: Success after binutils/gcc/gdb: 11 commits new e7ac82959b 445: onsuccess: #2148: 7: Success after binutils/gcc/linux/g [...] new 150b1cc989 446: onsuccess: #2: 7: Success after binutils/gcc/linux/gdb: [...] new 7b70568008 447: onsuccess: #2149: 7: Success after binutils/gcc/glibc/g [...] new d8d2deb79a 448: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] new 717e0c81c1 449: onsuccess: #4: 7: Success after binutils/gcc/gdb/qemu: [...] new d202727733 450: onsuccess: #5: 7: Success after binutils/gcc/linux/glib [...] 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 (7632f73c28) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 102 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: 01-reset_artifacts/console.log.xz | Bin 1752 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 31228 -> 31108 bytes 05-build_abe-stage1/console.log.xz | Bin 71768 -> 71424 bytes 07-build_abe-linux/console.log.xz | Bin 9120 -> 9596 bytes 08-build_abe-glibc/console.log.xz | Bin 244144 -> 243408 bytes 09-build_abe-stage2/console.log.xz | Bin 203436 -> 202828 bytes 10-build_abe-gdb/console.log.xz | Bin 39168 -> 38640 bytes 11-build_abe-qemu/console.log.xz | Bin 31800 -> 31896 bytes 12-check_regression/console.log.xz | Bin 4056 -> 4976 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++++++++++-------------- 22 files changed, 65 insertions(+), 65 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allyesconfig updated (5e4c957983 -> 7677c76272)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 5e4c957983 55: onsuccess: #540: 21422: Success after binutils/llvm/linu [...] new 7677c76272 56: onsuccess: #1: 21422: Success after binutils/llvm/qemu: [...] 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: 01-reset_artifacts/console.log.xz | Bin 1772 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31068 -> 31080 bytes 04-build_kernel_llvm/console.log.xz | Bin 64400 -> 67056 bytes 05-build_abe-qemu/console.log.xz | Bin 31732 -> 32380 bytes 06-build_linux/console.log.xz | Bin 3692 -> 3720 bytes 08-check_regression/console.log.xz | Bin 4448 -> 3952 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023