public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [commited][gdb/build] Fix gdb build with -fsanitize=thread and gcc 7
Date: Tue, 28 Jun 2022 17:07:57 +0200	[thread overview]
Message-ID: <92572357-17e1-0755-b536-98a6425bf0b9@suse.de> (raw)
In-Reply-To: <20220625090840.GA21429@delia.com>

On 6/25/22 11:08, Tom de Vries wrote:
> Hi,
> 
> When building gdb with system gcc 7.5.0, I run into:
> ...
> gdb/ia64-tdep.c: In function ‘int is_float_or_hfa_type_recurse(type*, type**)’:
> gdb/ia64-tdep.c:3362:1: error: control reaches end of non-void function \
>    [-Werror=return-type]
> ...
> 
> This is due to PR gcc/81275 - "-fsanitize=thread produce incorrect
> -Wreturn-type warning", which has been fixed in gcc-8.
> 
> Work around this by moving the default return outside the switch.
> 
> Tested on x86_64-linux.
> 
> Any comments?
> 

Committed.

Thanks,
- Tom

> [gdb/build] Fix gdb build with -fsanitize=thread and gcc 7
> 
> ---
>   gdb/ia64-tdep.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/gdb/ia64-tdep.c b/gdb/ia64-tdep.c
> index 82456dc9c98..b94225b5e13 100644
> --- a/gdb/ia64-tdep.c
> +++ b/gdb/ia64-tdep.c
> @@ -3356,9 +3356,10 @@ is_float_or_hfa_type_recurse (struct type *t, struct type **etp)
>         }
>         break;
>       default:
> -      return 0;
>         break;
>       }
> +
> +  return 0;
>   }
>   
>   /* Determine if the given type is one of the floating point types or

      reply	other threads:[~2022-06-28 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25  9:08 [PATCH][gdb/build] " Tom de Vries
2022-06-28 15:07 ` Tom de Vries [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=92572357-17e1-0755-b536-98a6425bf0b9@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).