linaro-toolchain

linaro-toolchain@lists.linaro.org

15 participants
5654 discussions

Re: [Linaro-TCWG-CI] gcc-16-4709-gc55c1de3a9a: 3 regressions on aarch64

by Jonathan Wakely

On Wed, 29 Oct 2025 at 22:04, <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_check master-aarch64, after: > | commit gcc-16-4709-gc55c1de3a9a > | Author: Jonathan Wakely <jwakely(a)redhat.com> > | Date: Tue Oct 28 12:15:52 2025 +0000 > | > | libstdc++: Simplify std::regex_traits::value > | > | We don't need to use an istringstream to convert a hex digit to its > | numerical value. And if we don't use istringstream there, we don't need > | to include <sstream> in <regex>. > | ... 8 lines of the commit log omitted. > > Produces 3 regressions: > | > | regressions.sum: > | Running g++:g++.dg/dg.exp ... > | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++11 (test for excess errors) > | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++17 (test for excess errors) > | FAIL: g++.dg/warn/uninit-pr105562.C -std=gnu++26 (test for excess errors) > > Used configuration : > *CI config* tcwg_gcc_check master-aarch64 > *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu > > We track this bug report under https://linaro.atlassian.net/browse/GNU-1735. Please let us know if you have a fix. > > If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. Fixed at r16-4714-gcc78f8523832d6 > > -----------------8<--------------------------8<--------------------------8<-------------------------- > > The information below contains the details of the failures, and the ways to reproduce a debug environment: > > You can find the failure logs in *.log.1.xz files in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4300/artifac… > The full lists of regressions and improvements as well as configure and make commands are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4300/artifac… > The list of [ignored] baseline and flaky failures are in > * https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4300/artifac… > > Current build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4300/artifac… > Reference build : https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/4299/artifac… > > Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/gcc/s… > > Full commit : See in git+ssh://linaroci@gcc.gnu.org/git/gcc.git

1 hour, 16 minutes

gcc-16-4069-ge77daa57300

by Paul Richard Thomas

The commit causing this regression was reverted three days later with r16-4111-g25f7f04e447dc0d2ed4c392eb21765e9ae9067d1 . Regards Paul

4 hours, 36 minutes

How the NI CLAD Certification Boosts Your Career in Engineering and Automation

by David Gibbs

Earning the NI Certified LabVIEW Associate Developer (CLAD) certification is a practical step for engineers and automation professionals aiming to prove hands-on LabVIEW competence. Employers value the problem-solving and system-design skills demonstrated by candidates who pass NI Certified LabVIEW Associate Developer CLAD Exam Questions, because the credential signals consistent coding practices and real-world application ability. The CLAD credential accelerates career growth by opening roles in test engineering, instrumentation, robotics, and industrial automation. With a firm foundation in graphical programming, certified professionals can contribute to project efficiency, reduce development time, and improve system reliability. Preparing with focused resources for NI Certified LabVIEW Associate Developer CLAD Exam Questions helps candidates master core topics such as dataflow, debugging, and modular design—skills directly transferable to workplace challenges. I selected Certboosters because it provides structured study plans, realistic practice tests, and expert feedback to increase confidence and exam readiness; their materials are tailored to practical outcomes and mirror exam style while reinforcing applied LabVIEW techniques. In short, the NI CLAD certification strengthens résumés, accelerates promotions, and equips engineers with an industry-recognized proof of LabVIEW proficiency that employers seek in automation and control-system roles. Use the link below to check the practice test questions: https://www.certboosters.com/ni/path/clad

11 hours, 49 minutes

Fwd: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed build (failure) (main)

by Mehdi AMINI

Hi folks, I have a strong suspicion that this bot has an incremental build issue right now. Can someone trigger a clean build please? Thanks! Mehdi ---------- Forwarded message --------- From: <llvm.buildmaster(a)lab.llvm.org> Date: Tue, Oct 28, 2025 at 12:51 AM Subject: ☠ Buildbot (LLVM Buildbot): flang-arm64-windows-msvc - failed build (failure) (main) To: Mehdi Amini <joker.eph(a)gmail.com> Cc: <llvm.buildmaster(a)lab.llvm.org> The Buildbot has detected a new failure on builder flang-arm64-windows-msvc while building flang,mlir. Full details are available at: https://lab.llvm.org/buildbot/#/builders/207/builds/9096 Worker for this Build: linaro-armv8-windows-msvc-01 Blamelist: Mehdi Amini <joker.eph(a)gmail.com> BUILD FAILED: failed build (failure) Step 5 (build-unified-tree) failure: build (failure) ... 359 | return {APFloat(*smt, value.real()), APFloat(*smt, value.imag())}; | ^ c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\complex(1315,5): note: 'complex' has been explicitly marked deprecated here 1315 | _DEPRECATE_NONFLOATING_COMPLEX | ^ c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\yvals_core.h(1450,7): note: expanded from macro '_DEPRECATE_NONFLOATING_COMPLEX' 1450 | [[deprecated("warning STL4037: " \ | ^ 1 warning generated. 84.583 [1719/10/276] Building CXX object tools/mlir/lib/Dialect/MemRef/IR/CMakeFiles/obj.MLIRMemRefDialect.dir/MemRefDialect.cpp.obj FAILED: tools/mlir/lib/Dialect/MemRef/IR/CMakeFiles/obj.MLIRMemRefDialect.dir/MemRefDialect.cpp.obj C:\Users\tcwg\scoop\shims\ccache.exe C:\Users\tcwg\scoop\apps\llvm-arm64\current\bin\clang-cl.exe /nologo -TP -DGTEST_HAS_RTTI=0 -DUNICODE -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS -D_GLIBCXX_ASSERTIONS -D_HAS_EXCEPTIONS=0 -D_SCL_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -D_UNICODE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/lib/Dialect/MemRef/IR -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/include -IC:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/llvm/include /DWIN32 /D_WINDOWS /Zc:inline /Zc:__cplusplus /Oi /Brepro /bigobj /permissive- -Werr or=unguarded-availability-new /W4 -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wno-pass-failed -Wmisleading-indentation -Wctad-maybe-unsupported /Gw -Wundef -Werror=mismatched-tags -Werror=global-constructors /O2 /Ob2 -std:c++17 -MD /EHs-c- /GR- -UNDEBUG /showIncludes /Fotools/mlir/lib/Dialect/MemRef/IR/CMakeFiles/obj.MLIRMemRefDialect.dir/MemRefDialect.cpp.obj /Fdtools\mlir\lib\Dialect\MemRef\IR\CMakeFiles\obj.MLIRMemRefDialect.dir\ -c -- C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR/MemRefDialect.cpp In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR/MemRefDialect.cpp:9: In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Conversion/ConvertToEmitC/ToEmitCInterface.h:14: In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OpDefinition.h:22: In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/Dialect.h:17: In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OperationSupport.h:19: C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/BuiltinAttributes.h(359,14): warning: 'complex' is deprecated: warning STL4037: The effect of instantiating the template std::complex for any type other than float, double, or long double is unspecified. You can define _SILENCE_NONFLOATING_COMPLEX_DEPRECATION_WARNING to suppress this warning. [-Wdeprecated-declarations] 359 | return {APFloat(*smt, value.real()), APFloat(*smt, value.imag())}; | ^ c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\complex(1315,5): note: 'complex' has been explicitly marked deprecated here 1315 | _DEPRECATE_NONFLOATING_COMPLEX | ^ c:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include\yvals_core.h(1450,7): note: expanded from macro '_DEPRECATE_NONFLOATING_COMPLEX' 1450 | [[deprecated("warning STL4037: " \ | ^ In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/lib/Dialect/MemRef/IR/MemRefDialect.cpp:12: In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Dialect/MemRef/IR/MemRef.h:13: In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Dialect/Arith/IR/Arith.h:17: In file included from C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Interfaces/ControlFlowInterfaces.h:371: C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include\mlir/Interfaces/ControlFlowInterfaces.h.inc(1118,84): error: no viable conversion from '::mlir::RegionSuccessor' to '::mlir::RegionBranchPoint' 1118 | return (llvm::cast<ConcreteOp>(tablegen_opaque_val)).getMutableSuccessorOperands(point); | ^~~~~ C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/build/tools/mlir/include\mlir/Interfaces/ControlFlowInterfaces.h.inc(435,23): note: in instantiation of member function 'mlir::detail::RegionBranchTerminatorOpInterfaceInterfaceTraits::Model<mlir::memref::AtomicYieldOp>::getMutableSuccessorOperands' requested here 435 | Model() : Concept{getMutableSuccessorOperands, getSuccessorRegions} {} | ^ C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Support/InterfaceSupport.h(238,46): note: in instantiation of member function 'mlir::detail::RegionBranchTerminatorOpInterfaceInterfaceTraits::Model<mlir::memref::AtomicYieldOp>::Model' requested here 238 | new (malloc(sizeof(InterfaceModel))) InterfaceModel(); | ^ C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Support/InterfaceSupport.h(225,7): note: in instantiation of function template specialization 'mlir::detail::InterfaceMap::insertModel<mlir::detail::RegionBranchTerminatorOpInterfaceInterfaceTraits::Model<mlir::memref::AtomicYieldOp>>' requested here 225 | insertModel<typename T::ModelT>(); | ^ C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/Support/InterfaceSupport.h(199,10): note: in instantiation of function template specialization 'mlir::detail::InterfaceMap::insertPotentialInterface<mlir::RegionBranchTerminatorOpInterface::Trait<mlir::memref::AtomicYieldOp>>' requested here 199 | (map.insertPotentialInterface<Types>(), ...); | ^ C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OpDefinition.h(1877,43): note: in instantiation of function template specialization 'mlir::detail::InterfaceMap::get<mlir::OpTrait::ZeroRegions<mlir::memref::AtomicYieldOp>, mlir::OpTrait::ZeroResults<mlir::memref::AtomicYieldOp>, mlir::OpTrait::ZeroSuccessors<mlir::memref::AtomicYieldOp>, mlir::OpTrait::OneOperand<mlir::memref::AtomicYieldOp>, mlir::OpTrait::HasParent<mlir::memref::GenericAtomicRMWOp>::Impl<mlir::memref::AtomicYieldOp>, mlir::OpTrait::OpInvariants<mlir::memref::AtomicYieldOp>, mlir::ConditionallySpeculatable::Trait<mlir::memref::AtomicYieldOp>, mlir::OpTrait::AlwaysSpeculatableImplTrait<mlir::memref::AtomicYieldOp>, mlir::MemoryEffectOpInterface::Trait<mlir::memref::AtomicYieldOp>, mlir::OpTrait::IsTerminator<mlir::memref::AtomicYieldOp>, mlir::RegionBranchTerminatorOpInterface::Trait<mlir::memref::AtomicYieldOp>, mlir::OpTrait::ReturnLike<mlir::memref::AtomicYieldOp>>' requested he re 1877 | return detail::InterfaceMap::template get<Traits<ConcreteType>...>(); | ^ C:/Users/tcwg/llvm-worker/flang-arm64-windows-msvc/llvm-project/mlir/include\mlir/IR/OperationSupport.h(533,55): note: in instantiation of member function 'mlir::Op<mlir::memref::AtomicYieldOp, mlir::OpTrait::ZeroRegions, mlir::OpTrait::ZeroResults, mlir::OpTrait::ZeroSuccessors, mlir::OpTrait::OneOperand, mlir::OpTrait::HasParent<mlir::memref::GenericAtomicRMWOp>::Impl, mlir::OpTrait::OpInvariants, mlir::ConditionallySpeculatable::Trait, mlir::OpTrait::AlwaysSpeculatableImplTrait, mlir::MemoryEffectOpInterface::Trait, mlir::OpTrait::IsTerminator, mlir::RegionBranchTerminatorOpInterface::Trait, mlir::OpTrait::ReturnLike>::getInterfaceMap' requested here Sincerely, LLVM Buildbot

13 hours, 51 minutes

Re: [Linaro-TCWG-CI] v6.17.3-130-g86f364ee5842: Failure on aarch64

by Nathan Chancellor

On Sun, Oct 26, 2025 at 05:01:16PM +0000, ci_notify(a)linaro.org wrote: > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In tcwg_kernel/llvm-master-aarch64-stable-allnoconfig, after: > | commit v6.17.3-130-g86f364ee5842 > | Author: Masahiro Yamada <masahiroy(a)kernel.org> > | Date: Thu Sep 18 10:05:46 2025 +0200 > | > | kbuild: always create intermediate vmlinux.unstripped > | > | [ Upstream commit 0ce5139fd96e9d415d3faaef1c575e238f9bbd67 ] > | > | Generate the intermediate vmlinux.unstripped regardless of > | ... 14 lines of the commit log omitted. This is reproducible for me locally with: $ make -skj"$(nproc)" ARCH=arm64 CC=clang CROSS_COMPILE=aarch64-linux-gnu- HOSTCC=clang LD=ld.lld clean allnoconfig all aarch64-linux-gnu-objcopy: vmlinux: file format not recognized ... This does not occur with llvm-objcopy via LLVM=1 nor does it happen with an all GNU setup. This feels like a bug in GNU objcopy though, as this is reproducible with: $ aarch64-linux-gnu-objcopy --set-section-flags .modinfo=noload vmlinux.unstripped vmlinux.objcopy $ file vmlinux.unstripped vmlinux.objcopy vmlinux.unstripped: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=18512f67dae70a7fae145b34514054a8b8b3c105, not stripped vmlinux.objcopy: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=18512f67dae70a7fae145b34514054a8b8b3c105, not stripped $ aarch64-linux-gnu-objcopy --remove-section=.modinfo -w --strip-unneeded-symbol='__mod_device_table__*' vmlinux.objcopy aarch64-linux-gnu-objcopy: vmlinux.objcopy: file format not recognized $ aarch64-linux-gnu-objcopy --version | head -1 GNU objcopy (GNU Binutils) 2.45.50.20251028 Cheers, Nathan

1 day, 1 hour

[Linaro-TCWG-CI] glibc-2.42.9000-284-g27effb3d50: 9 regressions on aarch64

by ci_notify＠linaro.org

Dear contributor, Our automatic CI has detected problems related to your patch(es). Please find some details below. In master-aarch64, after: | commit glibc-2.42.9000-284-g27effb3d50 | Author: Yury Khrustalev <yury.khrustalev(a)arm.com> | Date: Thu Sep 25 15:54:36 2025 +0100 | | aarch64: clear ZA state of SME before clone and clone3 syscalls | | This change adds a call to the __arm_za_disable() function immediately | before the SVC instruction inside clone() and clone3() wrappers. It also | adds a macro for inline clone() used in fork() and adds the same call to | ... 129 lines of the commit log omitted. Produces 9 regressions: | | regressions.sum: | Running gdb:gdb.threads/foll-fork-other-thread.exp ... | FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=auto: non-stop=off: displaced-stepping=auto: bt | FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=auto: non-stop=off: displaced-stepping=off: bt | FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=auto: non-stop=off: displaced-stepping=on: bt | FAIL: gdb.threads/foll-fork-other-thread.exp: fork_func=fork: follow=child: target-non-stop=off: non-stop=off: displaced-stepping=auto: bt | ... and 5 more Used configuration : *CI config* tcwg_gnu_native_check_gdb master-aarch64 *configure and test flags:* none, autodetected on aarch64-unknown-linux-gnu We track this bug report under https://linaro.atlassian.net/browse/GNU-1706. Please let us know if you have a fix. If you have any questions regarding this report, please ask on linaro-toolchain(a)lists.linaro.org mailing list. -----------------8<--------------------------8<--------------------------8<-------------------------- The information below contains the details of the failures, and the ways to reproduce a debug environment: You can find the failure logs in *.log.1.xz files in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… The full lists of regressions and improvements as well as configure and make commands are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… The list of [ignored] baseline and flaky failures are in * https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… Current build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… Reference build : https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--master-aarch64-build/1… Instruction to reproduce the build : https://gitlab.com/LinaroLtd/tcwg/ci/interesting-commits/-/raw/master/glibc… Full commit : https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=27effb3d50424fb9634b…

1 day, 11 hours

Re: [Linaro-TCWG-CI] gcc-16-4604-g8b9cd6490ce5: Failure on aarch64

by Sam James

This is now https://gcc.gnu.org/PR122456.

1 day, 13 hours

[PATCH] aarch64: streaming_mode_1.c: Remove dg-error

by H.J. Lu

On Tue, Oct 28, 2025 at 12:07 PM <ci_notify(a)linaro.org> wrote: > > Dear contributor, > > Our automatic CI has detected problems related to your patch(es). Please find some details below. > > In gcc_check master-aarch64, after: > | commit gcc-16-4667-gdcf69bdcd49 > | Author: H.J. Lu <hjl.tools(a)gmail.com> > | Date: Sun Oct 26 08:42:20 2025 +0800 > | > | c: Try the type with the previous function attributes > | > | When there are 2 conflicting function declarations, try the new type > | with the previous TYPE_ATTRIBUTES if the current declaration has no > | TYPE_ATTRIBUTES to support > | ... 44 lines of the commit log omitted. > > Produces 19 regressions: > | > | regressions.sum: > | Running gcc:gcc.target/aarch64/sme/aarch64-sme.exp ... > | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 10) > | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 121) > | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 16) > | FAIL: gcc.target/aarch64/sme/streaming_mode_1.c (test for errors, line 30) > | ... and 15 more > After commit dcf69bdcd49bccd901bfb01db7c15530e9a70dc0 Author: H.J. Lu <hjl.tools(a)gmail.com> Date: Sun Oct 26 08:42:20 2025 +0800 c: Try the type with the previous function attributes gcc no longer issues an error for: void sc_c () [[arm::streaming_compatible]]; void sc_c () {} Instead, the previous type attributes are applied to the current function definition. The resulting function definition is compatible with the previous declaration. PR c/122427 * gcc.target/aarch64/sme/streaming_mode_1.c: Remove dg-error. -- H.J.

1 day, 15 hours

Modify Your Cathay Pacific Flight Date Fast with Expert Phone Support

by jhase.20＠inwagit.com

Modify Your Cathay Pacific Trip Date Quickly by Phone – Call 1-833-341-5261 If your travel plans have changed and you need to update your Cathay Pacific flight, don’t worry—it’s easier than you might think. The quickest and most efficient way to change your flight date is by calling Cathay Pacific directly. Just dial 1-833-341-5261 to speak with a live customer service agent who can help you make the necessary changes in minutes. Whether you need to move your departure date, adjust your return trip, or accommodate a schedule change, Cathay Pacific’ phone support gives you direct access to real-time flight availability, fare options, and expert guidance. This method helps avoid the delays and confusion that can sometimes happen with online systems. Why Choose Phone Support? Changing your flight online is possible in some cases, but it’s not always the most reliable option—especially if: • Your itinerary involves multiple passengers or segments • You’re dealing with a complex schedule change • You want to compare multiple date options or explore cheaper alternatives • You need help understanding applicable fees or policies By calling 1-833-341-5261, you can speak to a real person who will walk you through the process, offer tailored suggestions, and make sure your new flight details are confirmed on the spot. It's a smart move if you’re short on time or want to avoid the hassle of navigating the website or app on your own. Step-by-Step: How to Change Your Flight by Phone Follow these simple steps to reschedule your Cathay Pacific trip with ease: 1. Prepare Your Booking Details Before calling, make sure you have all the necessary information ready to streamline the process. This includes: • Your booking reference number (also called a record locator) • Full names of all passengers on the reservation • The original flight date(s) and times • Your preferred new travel date(s) and timeframes • Any alternate dates you’d be willing to consider • Your payment method, in case there are fees or fare differences Having these details on hand ensures you won’t waste time looking for information during the call, which makes the process faster and more efficient. 2. Call Cathay Pacific at 1-833-341-5261 Once you’re ready, dial 1-833-341-5261 to connect with an Cathay Pacific representative. This dedicated line is designed to assist with flight changes, so you’ll be directed to the right department quickly. Pro Tip: To reduce wait times, try calling early in the morning or later in the evening, when call volume tends to be lower. Avoid peak hours around lunchtime and early afternoon if possible. 3. Speak to a Live Agent Once connected, clearly explain that you’d like to change your flight date. Provide the agent with: • Your reservation number • Passenger names • Original flight details • Your new preferred travel dates The agent will check availability in real-time and let you know what options are open for your revised itinerary. They’ll also inform you about any change fees or fare differences and help you compare flights if necessary. If you’re flexible with your dates or times, let the agent know—they may be able to find a better deal or more convenient option for you. 4. Pay Any Applicable Fees or Fare Differences In some cases, you may be required to pay: • A change fee, depending on your fare class • The fare difference, if your new flight costs more than your original one Some fares—especially basic economy—may have stricter change policies, while more flexible tickets may allow free changes. The agent will walk you through your options and provide a total cost before finalizing the change. Once you confirm the new itinerary and accept any applicable charges, you’ll securely provide your payment information over the phone. The agent will process the transaction and send you a confirmation email with your updated flight details. Tips for a Smooth Flight Change Process To make your call even more efficient, keep these tips in mind: • Call During Off-Peak Hours: Avoid long wait times by calling early in the morning or later in the evening. • Be Flexible: If you’re open to different dates or times, it increases your chances of finding better options or lower fares. • Ask About Fee Waivers: In some situations, like weather-related disruptions or schedule changes, fees may be waived. • Record the Agent’s Name and Confirmation Number: It’s always a good idea to keep a record of who you spoke with and your updated itinerary. • Double-Check Your Email: Once the change is processed, verify that the new flight details were sent to your email and are correctly reflected in your Cathay Pacific account. Frequently Asked Questions (FAQs) Are there change fees for all Cathay Pacific tickets? Not necessarily. Cathay Pacific has eliminated change fees on many domestic and short-haul international flights, especially for main cabin and premium cabin fares. However, basic economy tickets are usually non-changeable, and for certain international routes, change fees may still apply. Your phone agent will explain what applies to your specific fare. Yes. Cathay Pacific generally offers a 24-hour flexible booking policy, allowing you to change or cancel your flight within 24 hours of booking without penalty, as long as the booking was made at least 2 days before departure. What if I booked through a travel agency or third-party site? If you purchased your ticket through an online travel agency (like Expedia, Orbitz, or Priceline), or a physical travel agency, you may need to contact them directly for flight changes. Cathay Pacific customer service agents may not have access to modify third-party bookings. What happens if I miss my flight without calling? If you don’t notify the airline and simply miss your flight, your booking could be marked as a no-show. This often results in your entire itinerary being canceled with no refund or ability to change. If you know you won’t make your flight, call immediately to avoid penalties and preserve your options. Can I upgrade or downgrade when changing my flight? Yes, you can ask about available upgrades or changes in fare class when you reschedule. The agent can provide information on costs and availability for different seating classes, such as Main Cabin Extra, Premium Economy, Business, or First Class. Will my frequent flyer miles and status still apply after the change? Absolutely. As long as your updated itinerary is still with Cathay Pacific or its partner airlines, your Advantage miles and elite status benefits should still apply. Just double-check that your frequent flyer number is still attached to the new reservation. In Summary Changing your Cathay Pacific flight doesn’t have to be stressful or complicated. By calling 1-833-341-5261, you can get personalized assistance from a live agent who will walk you through the process and help you find the best new flight options. With real-time availability, secure payment processing, and helpful advice, phone support is one of the most effective ways to make changes quickly and confidently. So, if your plans have changed and you need to update your trip, don’t delay. Call Cathay Pacific today and modify your flight in just a few easy steps. The faster you act, the more options you’ll have—and the smoother your travel experience will be. 📞 Call Now: 1-833-341-5261 for Fast, Friendly Assistance

2 days, 14 hours

Phone Guide to Effortlessly Change Your Hawaiian Airlines Flight Date

by jhase.20＠inwagit.com

Modify Your Hawaiian Airlines Trip Date Quickly by Phone – Call 1-833-341-5261 If your travel plans have changed and you need to update your Hawaiian Airlines flight, don’t worry—it’s easier than you might think. The quickest and most efficient way to change your flight date is by calling Hawaiian Airlines directly. Just dial 1-833-341-5261 to speak with a live customer service agent who can help you make the necessary changes in minutes. Whether you need to move your departure date, adjust your return trip, or accommodate a schedule change, Hawaiian Airlines’ phone support gives you direct access to real-time flight availability, fare options, and expert guidance. This method helps avoid the delays and confusion that can sometimes happen with online systems. Why Choose Phone Support? Changing your flight online is possible in some cases, but it’s not always the most reliable option—especially if: • Your itinerary involves multiple passengers or segments • You’re dealing with a complex schedule change • You want to compare multiple date options or explore cheaper alternatives • You need help understanding applicable fees or policies By calling 1-833-341-5261, you can speak to a real person who will walk you through the process, offer tailored suggestions, and make sure your new flight details are confirmed on the spot. It's a smart move if you’re short on time or want to avoid the hassle of navigating the website or app on your own. Step-by-Step: How to Change Your Flight by Phone Follow these simple steps to reschedule your Hawaiian Airlines trip with ease: 1. Prepare Your Booking Details Before calling, make sure you have all the necessary information ready to streamline the process. This includes: • Your booking reference number (also called a record locator) • Full names of all passengers on the reservation • The original flight date(s) and times • Your preferred new travel date(s) and timeframes • Any alternate dates you’d be willing to consider • Your payment method, in case there are fees or fare differences Having these details on hand ensures you won’t waste time looking for information during the call, which makes the process faster and more efficient. 2. Call Hawaiian Airlines at 1-833-341-5261 Once you’re ready, dial 1-833-341-5261 to connect with an Hawaiian Airlines representative. This dedicated line is designed to assist with flight changes, so you’ll be directed to the right department quickly. Pro Tip: To reduce wait times, try calling early in the morning or later in the evening, when call volume tends to be lower. Avoid peak hours around lunchtime and early afternoon if possible. 3. Speak to a Live Agent Once connected, clearly explain that you’d like to change your flight date. Provide the agent with: • Your reservation number • Passenger names • Original flight details • Your new preferred travel dates The agent will check availability in real-time and let you know what options are open for your revised itinerary. They’ll also inform you about any change fees or fare differences and help you compare flights if necessary. If you’re flexible with your dates or times, let the agent know—they may be able to find a better deal or more convenient option for you. 4. Pay Any Applicable Fees or Fare Differences In some cases, you may be required to pay: • A change fee, depending on your fare class • The fare difference, if your new flight costs more than your original one Some fares—especially basic economy—may have stricter change policies, while more flexible tickets may allow free changes. The agent will walk you through your options and provide a total cost before finalizing the change. Once you confirm the new itinerary and accept any applicable charges, you’ll securely provide your payment information over the phone. The agent will process the transaction and send you a confirmation email with your updated flight details. Tips for a Smooth Flight Change Process To make your call even more efficient, keep these tips in mind: • Call During Off-Peak Hours: Avoid long wait times by calling early in the morning or later in the evening. • Be Flexible: If you’re open to different dates or times, it increases your chances of finding better options or lower fares. • Ask About Fee Waivers: In some situations, like weather-related disruptions or schedule changes, fees may be waived. • Record the Agent’s Name and Confirmation Number: It’s always a good idea to keep a record of who you spoke with and your updated itinerary. • Double-Check Your Email: Once the change is processed, verify that the new flight details were sent to your email and are correctly reflected in your Hawaiian Airlines account. Frequently Asked Questions (FAQs) Are there change fees for all Hawaiian Airlines tickets? Not necessarily. Hawaiian Airlines has eliminated change fees on many domestic and short-haul international flights, especially for main cabin and premium cabin fares. However, basic economy tickets are usually non-changeable, and for certain international routes, change fees may still apply. Your phone agent will explain what applies to your specific fare. Yes. Hawaiian Airlines generally offers a 24-hour flexible booking policy, allowing you to change or cancel your flight within 24 hours of booking without penalty, as long as the booking was made at least 2 days before departure. What if I booked through a travel agency or third-party site? If you purchased your ticket through an online travel agency (like Expedia, Orbitz, or Priceline), or a physical travel agency, you may need to contact them directly for flight changes. Hawaiian Airlines customer service agents may not have access to modify third-party bookings. What happens if I miss my flight without calling? If you don’t notify the airline and simply miss your flight, your booking could be marked as a no-show. This often results in your entire itinerary being canceled with no refund or ability to change. If you know you won’t make your flight, call immediately to avoid penalties and preserve your options. Can I upgrade or downgrade when changing my flight? Yes, you can ask about available upgrades or changes in fare class when you reschedule. The agent can provide information on costs and availability for different seating classes, such as Main Cabin Extra, Premium Economy, Business, or First Class. Will my frequent flyer miles and status still apply after the change? Absolutely. As long as your updated itinerary is still with Hawaiian Airlines or its partner airlines, your Advantage miles and elite status benefits should still apply. Just double-check that your frequent flyer number is still attached to the new reservation. In Summary Changing your Hawaiian Airlines flight doesn’t have to be stressful or complicated. By calling 1-833-341-5261, you can get personalized assistance from a live agent who will walk you through the process and help you find the best new flight options. With real-time availability, secure payment processing, and helpful advice, phone support is one of the most effective ways to make changes quickly and confidently. So, if your plans have changed and you need to update your trip, don’t delay. Call Hawaiian Airlines today and modify your flight in just a few easy steps. The faster you act, the more options you’ll have—and the smoother your travel experience will be. 📞 Call Now: 1-833-341-5261 for Fast, Friendly Assistance

2 days, 15 hours

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain