Recherche avancée

Médias (2)

Mot : - Tags -/kml

Autres articles (11)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
    Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Submit enhancements and plugins

    13 avril 2011

    If you have developed a new extension to add one or more useful features to MediaSPIP, let us know and its integration into the core MedisSPIP functionality will be considered.
    You can use the development discussion list to request for help with creating a plugin. As MediaSPIP is based on SPIP - or you can use the SPIP discussion list SPIP-Zone.

Sur d’autres sites (2197)

  • x86inc : Avoid using eax/rax for storing the stack pointer

    20 décembre 2016, par Henrik Gramner
    x86inc : Avoid using eax/rax for storing the stack pointer

    When allocating stack space with an alignment requirement that is larger
    
than the current stack alignment we need to store a copy of the original
    
stack pointer in order to be able to restore it later.
    

    If we chose to use another register for this purpose we should not pick
    
eax/rax since it can be overwritten as a return value.
    • [DH] libavutil/x86/x86inc.asm

  • x86inc : Avoid using eax/rax for storing the stack pointer

    8 octobre 2016, par Henrik Gramner
    x86inc : Avoid using eax/rax for storing the stack pointer

    When allocating stack space with an alignment requirement that is larger
    
than the current stack alignment we need to store a copy of the original
    
stack pointer in order to be able to restore it later.
    

    If we chose to use another register for this purpose we should not pick
    
eax/rax since it can be overwritten as a return value.
    • [DH] common/x86/x86inc.asm

  • checkasm : arm : preserve the stack alignment in x264_checkasm_checked_call

    14 novembre 2016, par Janne Grunau
    checkasm : arm : preserve the stack alignment in x264_checkasm_checked_call

    The stack used by x264_checkasm_checked_call_neon was a multiple of 4
    
when the checked function is called. AAPCS requires a double word (8 byte)
    
aligned stack public interfaces. Since both calls are public interfaces
    
the stack is misaligned when the checked is called.
    

    This can cause issues if code called within this (which includes
    
the C implementations) relies on the stack alignment.
    • [DH] tools/checkasm-arm.S

Navigation