Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] checkasm: Silence warnings about unused return value from read()
Date: Mon, 8 Aug 2022 23:39:57 +0300 (EEST)
Message-ID: <6b6fdd7c-91a6-c03a-6e6f-bc984e6fb326@martin.st> (raw)
In-Reply-To: <aeb8ae8c-4033-2ef8-404c-84777fb4528@martin.st>

On Fri, 5 Aug 2022, Martin Storsjö wrote:

> On Wed, 27 Jul 2022, Andreas Rheinhardt wrote:
>
>> Swinney, Jonathan:
>>> This patch looks good to me. I would appreciate its merging.
>>> 
>
>>  } while (0)
>>  #define PERF_STOP(t) do {                               \
>> +    int ret;                                            \
>>      ioctl(sysfd, PERF_EVENT_IOC_DISABLE, 0);            \
>> -    read(sysfd, &t, sizeof(t));                         \
>> +    ret = read(sysfd, &t, sizeof(t));                   \
>> +    (void)ret;                                          \
>>  } while (0)
>
>> Why do you use this extra variable instead of just casting the return
>> value of read to void?
>
> Because if I just cast the return value of read to void, it still warns about 
> it being unused, at least with GCC 9. I believe the rules for "used vs 
> unused" for variables (where you can cast it to void to mark it as used) and 
> "must not ignore return value" (-Wunused-result) differ. Apparently, in order 
> to appease the compiler for a return value to not be ignored, it either has 
> to be stored or compared.

Pushed this now.

// Martin
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

      reply	other threads:[~2022-08-08 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  7:43 Martin Storsjö
2022-07-27 18:02 ` Swinney, Jonathan
2022-07-27 18:09   ` Andreas Rheinhardt
2022-08-05  6:18     ` Martin Storsjö
2022-08-08 20:39       ` Martin Storsjö [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=6b6fdd7c-91a6-c03a-6e6f-bc984e6fb326@martin.st \
    --to=martin@martin.st \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git