Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec: add farbfeld encoder
Date: Mon, 3 Jun 2024 23:56:21 +0200
Message-ID: <GV1P250MB0737F673C7E9FE98A13067488FFF2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <2073001.WZ9lY2TYtf@basile.remlab.net>

Rémi Denis-Courmont:
> Le maanantaina 3. kesäkuuta 2024, 22.29.13 EEST marcus a écrit :
>>> Bogus cast / aliasing violation.
>>
>> I thought qualifiers don't affect aliasing rules in C. Am I wrong?
> 
> If they didn't, the compiler wouldn't warn about incompatible pointer type 
> conversions in the absence of the explict cast.
> 

Wrong: The conversion uint8_t*const*->const uint8_t * const* is safe
(indeed, C++ performs it automatically); the conversion
uint8_t*const*->const uint8_t ** (which is what the cast here does) is
safe from an aliasing point of view, but not
const-correct/-Wcast-qual-correct (cast to const uint8_t * const* instead).
It is a limitation of C not to be like C++ here.

- Andreas

_______________________________________________
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:[~2024-06-03 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03  3:27 Marcus B Spencer
2024-06-03  6:05 ` Rémi Denis-Courmont
2024-06-03 19:29   ` marcus
2024-06-03 19:38     ` Rémi Denis-Courmont
2024-06-03 21:56       ` Andreas Rheinhardt [this message]
2024-06-04  6:04         ` Rémi Denis-Courmont
2024-06-04  7:06           ` Andreas Rheinhardt
2024-06-04  7:19             ` Andreas Rheinhardt

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=GV1P250MB0737F673C7E9FE98A13067488FFF2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.com \
    --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