Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.
We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.
Thank you for your understanding.
Hi there,
I've noticed that MGD appears to base its cycle estimation on a Mali-T880 GPU. Is there a way to change the target GPU (to a Mali-400 in my case)?
The cycle estimates from Mali Offline Compiler differ significantly from the ones shown in MGD.
[INFO]: Using Mali-T880 r2p0 (Mali-T600_r13p0-00rel0) for shader compilation.Maximum ESSL version: 320.Supported extensions: GL_ARM_shader_framebuffer_fetch GL_ARM_shader_framebuffer_fetch_depth_stencil GL_EXT_shader_pixel_local_storage GL_OES_EGL_image_external GL_OES_gpu_shader5 GL_OES_texture_buffer GL_OES_texture_cube_map_array GL_ANDROID_extension_pack_es31a GL_EXT_color_buffer_half_float GL_EXT_color_buffer_float GL_KHR_blend_equation_advanced GL_OES_sample_variables GL_OES_shader_image_atomic GL_OES_shader_multisample_interpolation GL_OES_texture_storage_multisample_2d_array GL_EXT_geometry_shader GL_EXT_gpu_shader5 GL_EXT_primitive_bounding_box GL_EXT_shader_io_blocks GL_EXT_tessellation_shader GL_EXT_texture_buffer GL_EXT_texture_cube_map_array .
Thanks!
Yes, it's a good idea. I've added it to the requirements backlog, but it will need to get reviewed and prioritized by the product management team.
Cheers,Pete