Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Wang Bin <wbsecg1@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Weird cross platform support in ffmpeg
Date: Wed, 1 Jun 2022 00:38:35 +0800
Message-ID: <CAA4bkHYs-ezZbR1RbzYc9nfhHS8racFuanzOd=pOFuf75TJMLg@mail.gmail.com> (raw)
In-Reply-To: <YpYoyQFhoxsUbADu@phare.normalesup.org>

Nicolas George <george@nsup.org> 于2022年5月31日周二 22:40写道:

> Александр (12022-05-31):
> > I analyzed problem a little bit. Only gcc/clang allows to use this trick.
> > Msvc compiler forbidens such code (even with different enabled
> > optimizations like remove unused references, whole program optimization
> > etc) I have made patch, which uses preprocessor #if directive instead. If
> > it will be helpful, I can share the patch.
>
> FATE shows FFmpeg builds fine on several MSVC instances, so no, we do
> not need such a patch at this time.
>
> I have asked you to show on ffmpeg-users the exact thing you are
> attempting to do, you have neglected to do that. It is obvious to me
> that you are trying to tweak the build process in a way that is not
> supported: stop.
>
>
If MSVC whole program optimization is enabled (compiler flag /GL), DCE will
not work.
_______________________________________________
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".

      parent reply	other threads:[~2022-05-31 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 10:03 Александр
2022-05-31 10:10 ` Nicolas George
2022-05-31 14:14 ` Timo Rothenpieler
2022-05-31 14:23   ` Andreas Rheinhardt
2022-05-31 14:33     ` Александр
2022-05-31 14:40       ` Nicolas George
2022-05-31 14:52         ` Александр
2022-05-31 16:38         ` Wang Bin [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='CAA4bkHYs-ezZbR1RbzYc9nfhHS8racFuanzOd=pOFuf75TJMLg@mail.gmail.com' \
    --to=wbsecg1@gmail.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