[committed] driver: match up signal termination diagnostics

On Wed, 5 Aug 2026, Arsen Arsenović wrote:

> Alexander Monakov <[email protected]> writes:
> 
> > I just noticed the same message is present a few lines below what you patched,
> > under the 'default:' case label and with internal_error_no_backtrace instead of
> > fatal_error.
> >
> > I can probably push the obvious patch to fix that up, just let me know.
> 
> Sure, feel free to.

Pushed the following.

gcc/ChangeLog:

	* gcc.cc (execute) [default]: Use the same wording as above.
---
 gcc/gcc.cc | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/gcc/gcc.cc b/gcc/gcc.cc
index ca4e397bb5cb..973a34023305 100644
--- a/gcc/gcc.cc
+++ b/gcc/gcc.cc
@@ -3564,8 +3564,7 @@ execute (void)
 		 the user or OOM killer nuked it.  */
 	      fatal_error (input_location,
 			   "%s terminated by signal %d (%s)",
-			   commands[i].prog,
-			   WTERMSIG (status),
+			   commands[i].prog, WTERMSIG (status),
 			   strsignal (WTERMSIG (status)));
 	      break;
 
@@ -3588,9 +3587,9 @@ execute (void)
 
 	    default:
 	      /* The inferior failed to catch the signal.  */
-	      internal_error_no_backtrace ("%s signal terminated program %s",
-					   strsignal (WTERMSIG (status)),
-					   commands[i].prog);
+	      internal_error_no_backtrace ("%s terminated by signal %d (%s)",
+					   commands[i].prog, WTERMSIG (status),
+					   strsignal (WTERMSIG (status)));
 	    }
 	else if (WIFEXITED (status)
 		 && WEXITSTATUS (status) >= MIN_FATAL_STATUS)
-- 
2.51.0