Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] avutil/opt: Alpha workaround
Date: Wed, 1 Jun 2022 19:01:27 +0200
Message-ID: <20220601170127.GQ396728@pb2> (raw)
In-Reply-To: <165407988551.13099.15764009399381966957@lain>


[-- Attachment #1.1: Type: text/plain, Size: 1867 bytes --]

On Wed, Jun 01, 2022 at 12:38:05PM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2022-05-30 21:09:10)
> > alpha-linux-gnu-gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010 with qemu-alpha version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.39)
> > trigger a FPE on the DBL_MAX * 90000 operation
> > 
> > Iam not 100% sure why, but if i mess with mfp-trap-mode the compiler produces internal compiler errors
> > This issue seems not to affect the fate box with an older compiler
> > 
> > Ive also tried the gcc 6, gcc 7, gcc 8 packages with no luck
> 
> Do we event want to keep support for alpha? 

I have no opinion here


> Does it still have any
> real-world use? 

i do not know 


> It does not seem productive to spend development time on
> a dead platform.

Ive had the same thought and actually was a bit angry on myself after i spend
too long to get a gcc + qemu + gdb working together to debug this. Felt like
i could have done something more productive

I think a question is, is there someone who wants to maintain alpha support
because it seems it needs some support.
If someone does, its no work for me and i certainly dont mind if we keep alpha
on the list of supported architectures.
If not we can just apply this and pretend its still supported until it breaks
again. Though such support would not be with teh toolchain from the ubuntu
i used. The old fate box seems to work a lot better
Or we can just deprecate it and drop on a future bump
dont really have an opinion, but i dont plan to put any significant amount
of time in alpha support

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Homeopathy is like voting while filling the ballot out with transparent ink.
Sometimes the outcome one wanted occurs. Rarely its worse than filling out
a ballot properly.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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-06-01 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 19:09 Michael Niedermayer
2022-05-30 19:09 ` [FFmpeg-devel] [PATCH 2/2] avcodec/ffv1enc: " Michael Niedermayer
2022-06-01 10:38 ` [FFmpeg-devel] [PATCH 1/2] avutil/opt: " Anton Khirnov
2022-06-01 17:01   ` Michael Niedermayer [this message]
2022-06-06  7:55     ` Anton Khirnov

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=20220601170127.GQ396728@pb2 \
    --to=michael@niedermayer.cc \
    --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