Mark Kettenis wrote:
> I'm not sure to what extent this makes IBT less effective. Can the
> retpolines be used as gadgets to bypass IBT? Should we stop enabling
> retpolines by default?
>
> What *is* obvious is that retpolines are incompatible wuth shadow
> stacks. Is there an alternative
fr->cpu_opts.the_dct36 = dct36_x86_64;
> >
> > dct36_avx and dct36_x86_64 are assembly routines that lack the
> > endbr64 landing pad. And yet, on my IBT-enabled amd64 laptop,
> > mpg123 plays just fine with both the avx and x86_64 decoders.
>
> I ha
k the
> endbr64 landing pad. And yet, on my IBT-enabled amd64 laptop,
> mpg123 plays just fine with both the avx and x86_64 decoders.
I have examined the generated assembly on the calling side. There
is no "jmp *%r11" or such. Instead, calling the function pointer
goes thro
fr->cpu_opts.the_dct36 = dct36_avx;
> > ...
> > fr->cpu_opts.the_dct36 = dct36_x86_64;
> >
> > dct36_avx and dct36_x86_64 are assembly routines that lack the
> > endbr64 landing pad. And yet, on my IBT-enabled amd64 laptop,
> >
> fr->cpu_opts.the_dct36 = dct36_avx;
> ...
> fr->cpu_opts.the_dct36 = dct36_x86_64;
>
> dct36_avx and dct36_x86_64 are assembly routines that lack the
> endbr64 landing pad. And yet, on my IBT-enabled amd64 laptop,
> mpg123 plays j
t36 = dct36_x86_64;
dct36_avx and dct36_x86_64 are assembly routines that lack the
endbr64 landing pad. And yet, on my IBT-enabled amd64 laptop,
mpg123 plays just fine with both the avx and x86_64 decoders.
--
Christian "naddy" Weisgerber na...@mips.inka.de
This port has some infrastructure to use an optimized function that
uses a function pointer. Not sure why for arm64 it actually uses that
infrastructure, since the only alternative is the generic C
implementation. But adding a BTI instruction is the easiest fix.
ok?
Index: audio/mpg123
On Sat, Jun 12, 2021 at 11:20:19PM +0200, Christian Weisgerber wrote:
> Kurt Mosiejczuk:
> > The most recent version of mpg123 uses C99 for loop initialization.
> It already did before.
> The issue here is that upstream changed configure.ac to be compatible
> with autoconf 2.
Kurt Mosiejczuk:
> The most recent version of mpg123 uses C99 for loop initialization.
It already did before.
The issue here is that upstream changed configure.ac to be compatible
with autoconf 2.71, then went back and used 2.69.
* With 2.71, AC_PROG_CC tries to enable C89/C99/
The most recent version of mpg123 uses C99 for loop initialization.
This fixes the build for sparc64/base-gcc.
ok?
(cc maintainer)
--Kurt
Index: Makefile
===
RCS file: /cvs/ports/audio/mpg123/Makefile,v
retrieving revision 1.107
On 07/15/18 16:08, Christian Weisgerber wrote:
It looks like somebody wanted xmms2 to use fixed-point integer audio
decoders, maybe for use on old arm systems. I already switched the
port from tremor to vorbis, and I would now like to propose to use
libmpg123 over libmad. mpg123 is still
It looks like somebody wanted xmms2 to use fixed-point integer audio
decoders, maybe for use on old arm systems. I already switched the
port from tremor to vorbis, and I would now like to propose to use
libmpg123 over libmad. mpg123 is still maintained upstream and
also faster, in case somebody
The patch below builds mpg123's AVX decoder code on amd64.
Do we want this?
Like the other CPU-specific optimizations this is checked at runtime
and only enabled if the CPU/OS supports it, otherwise mpg123 will
fall back to the SSE decoder on amd64. Previously, I didn't enable
this because
On Thu, Dec 25, 2008 at 07:20:07PM +0100, Christian Weisgerber wrote:
This is a rough diff to enable the EsounD and JACK output plugins
that are included with mpg123. They are split out into subpackages,
and there are even pseudo-flavors do disable them since mpg123
itself has rather little
On Sun, Dec 28, 2008 at 05:38:16PM +0100, Alexandre Ratchov wrote:
jack is very different from esd/arts/pulse, it's a framework around
which apps for music are developped. IMO classic apps with audio
backends don't need jack backends as long as they can work without
jack. Advanced audio apps
On Thursday 25 December 2008 13:20:07 Christian Weisgerber wrote:
This is a rough diff to enable the EsounD and JACK output plugins
that are included with mpg123. They are split out into subpackages,
and there are even pseudo-flavors do disable them since mpg123
itself has rather little
On Sun, Dec 28, 2008 at 02:13:47AM -0500, Brad wrote:
On Thursday 25 December 2008 13:20:07 Christian Weisgerber wrote:
This is a rough diff to enable the EsounD and JACK output plugins
that are included with mpg123. They are split out into subpackages,
and there are even pseudo-flavors do
This is a rough diff to enable the EsounD and JACK output plugins
that are included with mpg123. They are split out into subpackages,
and there are even pseudo-flavors do disable them since mpg123
itself has rather little in the way of dependencies.
I haven't actually tried to use these output
On Thu, Dec 25, 2008 at 07:20:07PM +0100, Christian Weisgerber wrote:
This is a rough diff to enable the EsounD and JACK output plugins
that are included with mpg123. They are split out into subpackages,
and there are even pseudo-flavors do disable them since mpg123
itself has rather little
control
mode.
discovered the -C flag...
since few days i'm using mpg123 (instead of mpg321) and it worked
all the time.
The output module API isn't documented, so this involves a bit
of guesswork.
Turns out I guessed wrong for the flush primitive. Provide a dummy,
since this function
On Mon, Nov 10, 2008 at 12:38:54AM +0100, Christian Weisgerber wrote:
This is a first draft of a new port of mpg123 1.6.0, created from
scratch as a replacement for our cadaverous audio/mpg123 port.
works here, on i386 with various devices.
I have added a simple sndio backend. The output
New version:
* Update to 1.6.1.
* Integrate ratchov@'s sndio backend improvements.
* Enable IPv6 support.
Tested on alpha, amd64, arm, i386, sparc64.
I'd appreciate if somebody could give it a try on powerpc.
--
Christian naddy Weisgerber [EMAIL PROTECTED]
mpg123
On Mon, 10 Nov 2008, Christian Weisgerber wrote:
Tested on alpha, amd64, arm, i386, sparc64.
I'd appreciate if somebody could give it a try on powerpc.
It works fine after some slight testing on macppc.
--
Antoine
Christian Weisgerber [EMAIL PROTECTED] wrote:
New version:
* Update to 1.6.1.
* Integrate ratchov@'s sndio backend improvements.
* Enable IPv6 support.
* Fix next/previous/back to beginning of track in terminal control
mode.
The output module API isn't documented, so this involves a bit
This is a first draft of a new port of mpg123 1.6.0, created from
scratch as a replacement for our cadaverous audio/mpg123 port.
I have added a simple sndio backend. The output module API isn't
documented, so this involves a bit of guesswork. There is a function
to query the capabilities
Earin Gregor ha scritto:
Wohoo, so many answers.
As soon as I got some time at hand I'll try out all those suggestions.
Music formats I'm interested in are mainly mp3 and ogg.
And yes playlist support aswell as volume control would be cool indeed :-)
I have a almost done port for latest
for mpg123 but
I'm willing to test a possible update though.
Regards
Hi,
During my search for a console based mp3/ogg player I found mpg123. But it
seems quite old. The last version bump in the ports tree is already some
time ago. The same for mpg321.
Thus I wanted to ask if it is still actively maintained by someone?
Or is there some other console based music
On Fri, Jun 20, 2008 at 07:28:18PM +0200, Earin Gregor wrote:
During my search for a console based mp3/ogg player I found
mpg123. But it seems quite old. The last version bump in the ports
tree is already some time ago. The same for mpg321. Thus I wanted
to ask if it is still actively
Or is there some other console based music player which is overly
prefered by the people here? I'm open for suggestions :-)
Some people like audio/musicpd and its various clients.
I think Will meant audio/mpd, which is indeed a very good player.
-0-
--
I cannot conceive that anybody
On Fri, Jun 20, 2008 at 12:50:58PM -0500, Will Maier wrote:
On Fri, Jun 20, 2008 at 07:28:18PM +0200, Earin Gregor wrote:
During my search for a console based mp3/ogg player I found
mpg123. But it seems quite old. The last version bump in the ports
tree is already some time ago. The same
On Fri, Jun 20, 2008 at 07:28:18PM +0200, Earin Gregor wrote:
Hi,
During my search for a console based mp3/ogg player I found mpg123. But it
seems quite old. The last version bump in the ports tree is already some
time ago. The same for mpg321.
Thus I wanted to ask if it is still actively
Earin Gregor [EMAIL PROTECTED] wrote:
During my search for a console based mp3/ogg player I found mpg123. But it
seems quite old. The last version bump in the ports tree is already some
time ago. The same for mpg321.
The version of mpg123 in ports is very obsolete. The current release
needs
Jacob Meuser writes:
On Fri, Jun 20, 2008 at 07:28:18PM +0200, Earin Gregor wrote:
During my search for a console based mp3/ogg player I found
mpg123. But it seems quite old. The last version bump in the
ports tree is already some time ago. The same for mpg321.
Thus I wanted to ask
Deanna Phillips writes:
$ gst-launch-0.10 playbin uri=anything
Oh. That is from multimedia/gstreamer-0.10/core.
What I did was go into every multimedia/gstreamer-0.10 directory
and do 'make install-all'. I would really like to have a single
meta package that does this.
On Fri, Jun 20, 2008 at 08:08:26PM +, Deanna Phillips wrote:
Jacob Meuser writes:
On Fri, Jun 20, 2008 at 07:28:18PM +0200, Earin Gregor wrote:
During my search for a console based mp3/ogg player I found
mpg123. But it seems quite old. The last version bump in the
ports tree
On Sun, Dec 02, 2007 at 05:10:29AM -0800, Bryan Linton wrote:
On 2007-11-30 22:34:25, Jacob Meuser [EMAIL PROTECTED] wrote:
On Thu, Nov 29, 2007 at 03:00:10PM +, Christian Weisgerber wrote:
Giovanni Bechis [EMAIL PROTECTED] wrote:
Mpg123 updated to latest version,
files
Jacob Meuser wrote:
if the current port handles that gracefully, but the update doesn't, then
at least some of the patches are still needed. if neither handle that,
well, I guess it doesn't tell us much.
This update seems not to work with http streams, I will look at it as
soon as possible.
On 2007-11-30 22:34:25, Jacob Meuser [EMAIL PROTECTED] wrote:
On Thu, Nov 29, 2007 at 03:00:10PM +, Christian Weisgerber wrote:
Giovanni Bechis [EMAIL PROTECTED] wrote:
Mpg123 updated to latest version,
files/* and patches/* are no more needed to build,
I looked into updating
On Thu, Nov 29, 2007 at 03:00:10PM +, Christian Weisgerber wrote:
Giovanni Bechis [EMAIL PROTECTED] wrote:
Mpg123 updated to latest version,
files/* and patches/* are no more needed to build,
I looked into updating mpg123 a while back but got bogged down
because the port has
Giovanni Bechis [EMAIL PROTECTED] wrote:
Mpg123 updated to latest version,
files/* and patches/* are no more needed to build,
I looked into updating mpg123 a while back but got bogged down
because the port has substantial audio-related patches my Marc
Espie, and the function of these patches
Mpg123 updated to latest version,
files/* and patches/* are no more needed to build,
support to arch without fpu (arm) has been added but should
be tested.
Tested @i386
Giovanni
Index: Makefile
===
RCS file: /cvs/ports/audio/mpg123
can't builded in openbsd snapshots i386
IBM-ThinkPad-570Time:9:31am[/usr/ports/audio/mpg123]-root-make install clean
=== Checking files for mpg123-0.68
`/usr/ports/distfiles/mpg123-0.68.tar.gz' is up to date.
(SHA256) mpg123-0.68.tar.gz: OK
=== Verifying specs: c m c m
=== found c.42.0 m.2.3
IBM-ThinkPad-570Time:9:36am[/usr/ports/audio]-root-patch -d mpg123
/data/patch/mpg123.diff
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|Index: Makefile
|===
|RCS file: /cvs
need remove /usr/ports/audio/mpg123/patches directory.
builded on i386 ok
--
No self-respecting fish would want to be wrapped in that kind of
paper.
-- Mike Royko on the Chicago Sun-Times after it was
taken over by Rupert Murdoch
45 matches
Mail list logo
