From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec: add farbfeld encoder
Date: Tue, 04 Jun 2024 09:04:41 +0300
Message-ID: <D56BAB28-51F3-4E9B-B73C-8DA65F4E88E0@remlab.net> (raw)
In-Reply-To: <GV1P250MB0737F673C7E9FE98A13067488FFF2@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
Le 4 juin 2024 00:56:21 GMT+03:00, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> a écrit :
>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
Nope. The pointer types have the same representation and in practice neither LLVM IR nor GIMPLE can differentiate them, but they are not compatible according to spec (C11 §6.7.6.1).
You can convert `const uint8_t **` to `const uint8_t *const *`, for sure (C11 §6.3.2.3), but that's not the same conversion
_______________________________________________
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".
next prev parent reply other threads:[~2024-06-04 6:04 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
2024-06-04 6:04 ` Rémi Denis-Courmont [this message]
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=D56BAB28-51F3-4E9B-B73C-8DA65F4E88E0@remlab.net \
--to=remi@remlab.net \
--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